Print Page | Close Window

[SOLVED] App Suddenly Broken!

Printed From: IdeaBlade
Category: DevForce
Forum Name: DevForce Classic
Forum Discription: For .NET 2.0
URL: http://www.ideablade.com/forum/forum_posts.asp?TID=462
Printed Date: 11-Jun-2026 at 6:01pm


Topic: [SOLVED] App Suddenly Broken!
Posted By: Linguinut
Subject: [SOLVED] App Suddenly Broken!
Date Posted: 02-Oct-2007 at 1:34pm
I opened one of my application projects, double-clicked a view to work on and was faced with the white screen of death.  No panic.  I rebuilt.  Wham!!  Tons of errors...over 7000 like this:
 
The type or namespace name 'IdeaBlade' could not be found (are you missing a using directive or an assembly reference?)
 
Ok.  Close IDE and reopen.  Rebuild.  Same set of errors.  All references look fine.  Versions are good.  Physical files actually exist in the location specified. 
 
Not sure what to do from this point.
 
Please note:  this is not a CAB application.


Replies:
Posted By: Linguinut
Date Posted: 02-Oct-2007 at 1:49pm
Remove all references to all IdeaBlade assemblies and readd them.
 
That is what I did to fix the problem.  Now, can anyone venture why this may have occurred?

Posted By: davidklitzke
Date Posted: 02-Oct-2007 at 2:05pm
You had the "Specific Version" property of your references set to "True".  You may fixed your problem the wrong way.  You should set the "Specific Version" property of your references to False.

Posted By: Linguinut
Date Posted: 02-Oct-2007 at 2:13pm

I found the reference to "Specific Version" on page 492 (last page) of the Developers Guide.   It states:

This is a bizarre artifact of Visual Studio 2005 that only occurs for some projects after you’ve upgraded versions of software and / or upgraded Visual Studio or .NET itself.

We’ve seen it with IdeaBlade.Util. We’ve seen it with references to 3rd party assemblies (e.g., nunit.framework) as well.

We have not figured out why it happens but it is easy to address.

š    Remove the reference from your project.

š    Re-add the reference.

š    Re-build the project.

š    Remember to set “Specific Version” to “false”.

 
 
Oddly enough, I did not upgrade DevForce or Visual Studio, so something else must be amiss within that project.  I will set these assemblies "Specific Version" properties to false, though.  Preventative measure.
 


Print Page | Close Window