Home
Help
Register
Log in

Search

 
   Active Threads  

You are here: Home > LLBLGen Pro > Bugs & Issues> Assembly 'C:\WindowsProjects\Weld\Weld2\Weld.Facade\bin\Debug\Weld.ORM.dll' must be strong signed in order to be marked as a prerequisite.
 

Pages: 1
Bugs & Issues
Assembly 'C:\WindowsProjects\Weld\Weld2\Weld.Facade\bin\Debug\Weld.ORM.dll' must be strong signed in order to be marked as a prerequisite.
Page:1/1 

  Print all messages in this thread  
Poster Message
Dan1
User



Location:

Joined on:
20-Sep-2007 16:09:06
Posted:
41 posts
# Posted on: 21-Sep-2009 16:43:48.  
LLBLGen Pro 2.5

We get this error for the ORM project in Visual Studio 2008 now and again. This doesn't happen with any other projects other than the LLBLGen Pro generated project.

What is the best way to resolve this? Do we need to absolutely strong name this?
  Top
daelmo
Support Team



Location:
Guatemala City
Joined on:
28-Nov-2005 23:35:24
Posted:
8138 posts
# Posted on: 22-Sep-2009 04:07:54.  
Dan1, Are you using your own copy of LLBLGen ORMSupportClasses source code instead of the runtime libraries?

Seems like you are using the ORM sourcecode, modifying it, and trying to compile it. That source comes with a strong key. You should get ride of it or generate your own strong key signature.

If that is true, Is there any special reason you are using the source code instead of the compiled runtime libraries?


David Elizondo
LLBLGen'ing (articles and code snippets) | linkedin | twitter
 
Top
joshlrogers
User



Location:

Joined on:
06-Aug-2009 21:56:11
Posted:
10 posts
# Posted on: 08-Oct-2009 18:13:08.  
daelmo,

We just upgraded to VS 2008 and now we are experiencing the same issue. We are not using the source code rather we are using the compiled runtime libraries. Could you please advise?

Also, this only happens when the configuration is set to debug when set to release it does not produce this error.

Thank you,
Josh Rogers
  Top
joshlrogers
User



Location:

Joined on:
06-Aug-2009 21:56:11
Posted:
10 posts
# Posted on: 08-Oct-2009 18:46:00.  
For future reference, I have found the solution to this problem.

For some reason one of the projects was marked to not build in the configuration manager. This project referenced the orm support classes. This is what caused the issue. I don't know how or why the build checkbox got unchecked as I am the only one who could have changed that but at least this provides a solution.

I have found this seems to be an issue that happens fairly common at least when searching using google.

Anyways, hope this helps.

Thanks,
Josh Rogers


  Top
Pages: 1  


Powered by HnD ©2002-2007 Solutions Design
HnD uses LLBLGen Pro

Version: 2.1.12172008 Final.