NuGet does not allow me to go back to previous versions about keralua HOT 9 CLOSED

You are correct. It seems there is something strange with the sn. I will take a look into that. Thank you for your report @UweKeim

from keralua.

which version specifically? The previous version has a bug where the nuspec file was including lua53.dll as a .NET framwork dll. The latest version should work, if isn't working we should fix and update, not downgrade 😉
How can I repro the issue?

from keralua.

Also, the listing is only for search.
If you really want to target old versions just point the old version on PackageReference or package.config and use NuGet restore.

https://support.appharbor.com/discussions/problems/2959-downloading-unlisted-nuget-packages

from keralua.

This seem to be an error with the strong name assembly signature.

https://forums.asp.net/t/1168781.aspx?+Strong+name+signature+could+not+be+verified+

from keralua.

• Fixed: https://github.com/NLua/KeraLua/releases/tag/v1.0.4

from keralua.

What a fast fix, thank you very much!

from keralua.

Thanks, Vinicius

I honestly don't know. The build command that does bring up the error in #40 is:

"C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\msbuild.exe" "C:\MyProject\MySolution.sln" /p:Configuration=Release;optimize=true;MvcBuildViews=true /t:Clean;Rebuild

And to quote the error again, it is:

ASPNETCOMPILER : error ASPCONFIG: Die Datei oder Assembly "KeraLua, Version=1.0.3.0, Culture=neutral, PublicKeyToken=6a194c04b9c89217" oder eine Abhängigkeit davon wurde nicht gefunden. Die Signatur mit starkem Namen konnte nicht überprüft werden. Die Assembly wurde möglicherweise geändert oder verzögert aber nicht vollständig mit dem richtigen privaten Schlüssel signiert. (Ausnahme von HRESULT: 0x80131045) [c:\MyProject\MyMvcApplication.csproj]

What stands out here to me is the "ASPNETCOMPILER" and "error ASPCONFIG".

Seems that the error is no "normal" compilation error but something related to ASP.NET MVC. I'm using .NET Framework 4.5.2.

Since the project runs normally when compiling from within Visual Studio 2017 and the error only seems to occur with the "MvcBuildViews" parameter for msbuild.

In case it helps, this is the web.config file for the project that failes to compile.

If I change "MvcBuildViews=true" to "MvcBuildViews=false", the msbuild command succeeds. But after all, I do want to also build all views to get any potential errors in CSHTML files, too.

from keralua.

I've created a new project from scratch to reproduce the error:

Dropbox download link of ZIP

There are two batch files:

• "build-fail.cmd" to illustrate the msbuild error.
• "build-success.cmd" to illustrate the msbuild success., when setting "MvcBuildViews=false".

I was able to reproduce the error with the above ZIP on two independent machines.

from keralua.

Thanks. From what I read from your forum link, this is something that has to be done on your side, not mine.

Correct?

from keralua.