We developed an asp.net 3.5 application, which consists of a website, some developed assemblies and some third-party assemblies, such as Telerik, Jayrock, etc., and all these are very standard third-party applications.
Created and built this application, tested in Win 2008 Eval, running on a virtual machine, everything is fine. Imagine my disappointment when, after installing the server on the Win 2008 client server, that the application could not work, and the error message was "Strong signature could not be verified. Perhaps the assembly was changed or it was signed with a delay ..." one. This was for all assemblies in the application (one was removed, and it continued to appear for another assembly). Trying to install on a machine on the network and get the same error. I am rather puzzled and a little excited as I cannot figure it out and time is running out quickly. Inspected all parts of the server that I know about (.NET, IIS7), but everything seems fine.
What could be the reason for this? It looks like there is a stricter security manifest on the production server, but where would I look and for what? This should be a group policy. the only other element is that Symantec antivirus is running on computers.
The IT manager is in the halls, so he cannot try it out, which is also frustrating, but as they say, time does not wait for anyone!
source
share