[RESOLVED] [2003] resource files in obj folder causing issues

[kleinma]

I am having no luck today

All of a sudden I am having an issue with my app that has been working just fine all along.

I keep getting an error that references .resource files in the obj folder...

Sure enough.. sometimes they are gone, sometimes they are there.

I have to close VS.NET, and reopen.. rebuild my project, and then it generally will work, but then if I close VS, reopen it, and open my project, and try to open the form in the designer.. same error again. I have to close the form, rebuild, and then I can open the form properly.

When I run the application, it works fine, and all controls are there.

I did change some namespaces around, but it was working after I made those changes.

Could not find type 'my controls type'. Please make sure that the assembly that contains this type is referenced. If this type is a part of your development project, make sure that the project has been successfully built.

Also if the form is open in the designer when I rebuild, and this error occurs, it simply deletes all my controls off the form, and I have to add them all over again.

I doubt anyone has come across this, and I found little to no help searching around the web, but I have no idea how to try to fix this.

[RobDog888]

I would get a similar issue with missing controls when I was working on my Panel user control that you helped me with a year or two ago. Right now I cant remember what fixed it but it did use some namespaces. Did you already install SP1?

[ComputerJy]

That's why I like the "Clean" build in VS2005.
Did you try installing the VS SP1? It really fixes lots of bugs in that IDE.
Anyway, whenever that problem happened to me; I used to delete the 'bin' & 'obj' folders from the project path and magically everything back to working just fine

[kleinma]

Yeah I have SP1 installed. This project was working no problem up until today.

The only thing I did today, was strong name the assemblies, and also changed some of the namespacing.

I think I am going to try to take off the strong naming for now and see if that fixes it, although this is a very odd error, because its intermittent, and it really seems more of a bug than something I did wrong.

[kleinma]

That's why I like the "Clean" build in VS2005.
Did you try installing the VS SP1? It really fixes lots of bugs in that IDE.
Anyway, whenever that problem happened to me; I used to delete the 'bin' & 'obj' folders from the project path and magically everything back to working just fine

Just to verify, is SP1's version number of the IDE 7.1.6030?

Also, I already tried deleting the bin and obj folders, they get recreated just fine, but the problem still persists...

[RobDog888]

I think you are also using VSS? If so pull up a version history and do a comparison between yesterdays version and todays. The differences are color coded as you probable know but it makes it really easy to see where things may have gone wrong, if its not a MS IDE bug.

[kleinma]

I have found this KB article, however they require you contact them directly to get the fix, you can't download it.

http://support.microsoft.com/kb/842706

I am not even convinced this will solve my problem, as like I said, this just started all of a sudden, and since I deleted the bin/obj folders, I have not put anything in release mode.

[kleinma]

I think you are also using VSS? If so pull up a version history and do a comparison between yesterdays version and todays. The differences are color coded as you probable know but it makes it really easy to see where things may have gone wrong, if its not a MS IDE bug.

I only have VSS hooked up for 2005

[RobDog888]

Thats a good KBA but I would assume that the fix was included in SP1?

[kleinma]

I would think so.. my DLL version is higher than the one they mention...

I think to avoid pulling more of my hair out, I will just do the somewhat tedious process of creating a new projects and copying my code over....

This has to be a bug... when I select rebuild all and get the error messages, and select rebuild all again it generally works.. That can't be a problem with my code, it has to be a bug.

[ComputerJy]

Strong naming always gave me a headache with 2003 but I most of my problems got fixed with the SP1
Your problem is really odd since you installed the SP.

Did you install any controls or components on the VS after updating it?

[ComputerJy]

I have found this KB article, however they require you contact them directly to get the fix, you can't download it.

http://support.microsoft.com/kb/842706

I am not even convinced this will solve my problem, as like I said, this just started all of a sudden, and since I deleted the bin/obj folders, I have not put anything in release mode.

"Sorry, the page you requested is not available."
The link doesn't work

[kleinma]

No.

Nothing new has been installed whatsoever between this working and not working.

the ONLY 2 things I did were

1) Changed namespaces a little bit (but everything was still working after that)
2) Did strong naming of assembiles

I have since removed the strong naming, but still the issue persists...

Sometimes it refuses to create the files in the obj folder when I compile the app, sometimes it doesn't...

its a very odd issue indeed.

[RobDog888]

"Sorry, the page you requested is not available."
The link doesn't work

Link works fine for me using IE 6

[ComputerJy]

Link works fine for me using IE 6

I have FF and IE7 and it didn't work on either one

But back to the main issue, you can use the "pre-build event" to always delete the 'obj' folder.

Is the project your working on a website?

[kleinma]

no this is a windows forms app.

deleting the obj folder doesn't fix the problem.

I am just going to make the project over again. It should only take me about an hour or so since I have all the source and the solution structure. I just need to recreate it all.

[kleinma]

ok since today was monday and I wanted to get a fresh start on things, I recreated my project from scratch (although copy and paste was 95% of the work as far as coding goes). However I came up with my full namespace naming scheme ahead of time and named things correctly from the get go. I strong named all the assemblies from the start as well.

So far so good. I have no had the same issue (although I just finished and tested). Hopefully it will remain like this and I can attribute the issue to a bug that only shows its ugly face in rare situations.

Marking resolved.. for now