In previous posts, referred to in

http://www.llblgen.com/tinyforum/Messages.aspx?ThreadID=1169

people have issues with signed assemblies in the bin folder.

The solutions are 1) changes rights to the microsoft.net folder, 2) keep other apps from touching certain folders, i.e., antivirus and indexing, and/or 3) register the signed assemblies in the GAC and keep them out of the bin folder.

This customer will allow none of the above. They studiously avoid the GAC because they run so many websites and prefer people keep their things to themselves in their own bin folders. Numbers one and two are absolutely out.

So, any way to get unsigned copies of the dlls? I don't recall what source you offer, but can I build them? I know the one it's current vexing me on is SD.LLBLGen.Pro.DQE.SqlServer.NET11, but I have to wonder if, once I cleared that, SD.LLBLGen.Pro.ORMSupportClasses.NET11.dll will also bite me.

Is it possible to create a new folder in your installer area for unsigned copies of the runtime libraries, like "C:\Program Files\Solutions Design\LLBLGen Pro\RuntimeLibraries\DotNet11Unsigned"?

The anti-virus issue is a real issue, which has no relation with signed assemblies. Avoid virus-scanners scan/monitor bin folders, otherwise assemblies will get locked/recompile a lot.

if you don't want to use the signed versions, you can build your own. This is easy. Download the runtime sourcecode (or use the one in your llblgen pro folder). In there you'll find easy build scripts, like makeall11.cmd, which builds the code on the command line. Just create 2 folders in the folder of the runtime sourcecode: DotNet10 and DotNet11.

The assemblyinfo files contain a line with a key filename. Remove that line from all assembly info files. Then run the buildcommand script, and you'll have release builds for all assemblies, but not signed.

Then, recompile your application (incl. generated code) with these runtime libs.

http://www.llblgen.com/pages/secure/filestreamer.aspx?filename=RuntimeLibraries_Source_11032004.zip

You can download this source and comment out the signature stuff in the AssemblyInfo.cs file. The only projects you need to build are the ORM and the SQLDQE, you can remove the rest of them form the solution. I had to do this just yesterday.

[edit] Opps, I guess I was a little late with this one... Sorry! [/edit]

Thanks, I'll give that a try and see if that takes care of it.

These people have some weird rules (these are the 'we hate PKs and FKs' people). For instance , they also won't allow FrontPage Server Extensions. They're mainframe people converting downward, and anything that has magnitization is a potential threat. Corporate policy: "If it moves, study it for a month and maybe it will go away."

Thanks.

Built them unsigned, everything worked. This solves the issue.

Go figure. So, basically, I can now shove any b*stard .dll in there I want, no signiture required. In fact, the more I bypass signitures and security, the better off I am.

Story of my life.

Really odd policy these people have... You'd expect them to be as keen on security as possible. But then again, sometimes the wrong people are at the buttons and without a clue decide what has to be done... (like demanding everything to be tested on a testwebserver for WEEKS because it has to be solid and reliable but at the same time forgetting to run the latest IIS security patches...)