Home
Help
Register
Log in

Search

 
   Active Threads  

You are here: Home > LLBLGen Pro > Bugs & Issues> CS0006
 

Pages: 1
Bugs & Issues
CS0006
Page:1/1 

  Print all messages in this thread  
Poster Message
Rhywun
User



Location:
NYC
Joined on:
05-Jan-2005 02:17:57
Posted:
44 posts
# Posted on: 29-Sep-2005 16:56:56.  
I'm receiving this error when I load my website after about every 4th time I compile:

Code:

Compiler Error Message: CS0006: Metadata file 'c:\winnt\microsoft.net\framework\v1.1.4322\temporary asp.net files\...\sd.llblgen.pro.ormsupportclasses.net11.dll' could not be found


I have seen two possible causes listed here in the forums:

1. <identity impersonate="true" /> in the config file
2. strong-named assembly is in the bin folder

My question is:

Do BOTH of these items have to be corrected to stop this error? Should I bother trying to fix #2 if I cannot do anything about #1?? In other words, I DO NOT want to change the impersonation.
Self-Servicing, LLBLGenPro v. 2.5.0.0
ORMSupportClasses.NET20.dll v. 2.5.0.0
.NET v. 2.0.50727, VS v. 8.0.50727.51
 
Top
Drewes
User



Location:
Columbus, Ohio
Joined on:
18-Aug-2003 15:25:34
Posted:
67 posts
# Posted on: 30-Sep-2005 04:10:50.  
From what I have been able to find is that this problem can occur if signed assemblies are not in the GAC.
You may want to give that a try .
See this link:
http://www.waka.dk/Blog/PermaLink,guid,80d161fa-2124-45bd-9228-af3e16a003e9.aspx



  Top
Rhywun
User



Location:
NYC
Joined on:
05-Jan-2005 02:17:57
Posted:
44 posts
# Posted on: 03-Oct-2005 19:42:13.  
Well I have tried to compile the source code without the strongname key - it compiles but the web page which references my compiled version hangs forever.

I'm not messing with the GAC - I don't want to go down that road.

So I give up. Doing an 'iisreset' every few compiles is less trouble than any other solution, it seems.
Self-Servicing, LLBLGenPro v. 2.5.0.0
ORMSupportClasses.NET20.dll v. 2.5.0.0
.NET v. 2.0.50727, VS v. 8.0.50727.51
 
Top
Otis
LLBLGen Pro Team



Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
37377 posts
# Posted on: 03-Oct-2005 20:24:15.  
It's one of the many stupid errors in vs.net 2003. I can't help you with that further. What I do find odd is that if you compile the runtimes yourself (thus use the unsigned version), the code hangs...

Frans Bouma
LLBLGen Pro / ORM Profiler Lead Developer | Blog | Twitter
 
Top
Rhywun
User



Location:
NYC
Joined on:
05-Jan-2005 02:17:57
Posted:
44 posts
# Posted on: 04-Oct-2005 19:37:41.  
Otis wrote:
What I do find odd is that if you compile the runtimes yourself (thus use the unsigned version), the code hangs...


Well, it's entirely possible I did it wrong. I think what I did was, took your file named 'AssemblyInfoDotNet11.cs', removed the strong key file name, renamed it 'AssemblyInfo.cs', and compiled.
Self-Servicing, LLBLGenPro v. 2.5.0.0
ORMSupportClasses.NET20.dll v. 2.5.0.0
.NET v. 2.0.50727, VS v. 8.0.50727.51
 
Top
Otis
LLBLGen Pro Team



Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
37377 posts
# Posted on: 04-Oct-2005 20:21:51.  
Rhywun wrote:
Otis wrote:
What I do find odd is that if you compile the runtimes yourself (thus use the unsigned version), the code hangs...


Well, it's entirely possible I did it wrong. I think what I did was, took your file named 'AssemblyInfoDotNet11.cs', removed the strong key file name, renamed it 'AssemblyInfo.cs', and compiled.

With the project file in vs.net? It should have the same code then. But also compile the DQE of your choice, as it references the ormsupportclasses.



Frans Bouma
LLBLGen Pro / ORM Profiler Lead Developer | Blog | Twitter
 
Top
Rhywun
User



Location:
NYC
Joined on:
05-Jan-2005 02:17:57
Posted:
44 posts
# Posted on: 10-Nov-2005 18:09:20.  
Otis wrote:
With the project file in vs.net? It should have the same code then. But also compile the DQE of your choice, as it references the ormsupportclasses.


OK, I've finally revisited this a little more intelligently. Compiled both SD.LLBLGen.Pro.DQE.SqlServer.NET11 and SD.LLBLGen.Pro.ORMSupportClasses.NET11 without the strong key, reset references, rebuilt my projects and VOILA - CS0006 has gone away without an iisreset. Let's hope it stays that way! Thanks

PS. One of my earlier troubles was that I didn't realize the makefiles were using AssemblyInfoDotNet11.cs -- I mistakenly thought I had to rename it to 'AssemblyInfo.cs'.
Self-Servicing, LLBLGenPro v. 2.5.0.0
ORMSupportClasses.NET20.dll v. 2.5.0.0
.NET v. 2.0.50727, VS v. 8.0.50727.51
 
Top
Otis
LLBLGen Pro Team



Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
37377 posts
# Posted on: 10-Nov-2005 18:51:43.  
Yeah, you should use the proper makefiles, there's one for each .NET type Regular Smiley

Frans Bouma
LLBLGen Pro / ORM Profiler Lead Developer | Blog | Twitter
 
Top
Pages: 1  


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

Version: 2.1.12172008 Final.