The designer could not be shown for this file ... in VS 2003 - Please HELP!

Here is what I did to remedy the problem on my system:

1. Uninstalled Visual Studio.NET and any related programs that get
installed with Visual Studio.NEt (Framework 1.1, etc.)

2. Deleted the directory C:\Documents and Settings\Administrator\Local
Settings\Application Data\Microsoft\VisualStudio. Repeat this for the
"All Users" directory under "Documents and Settings".

3. Removed any applications that had anything to do with eVB, eVC,
CompactFramework, SmartPhone SDK, etc.

4. Removed any residual directories on the hard drive that had to do
with eVB, eVC, CompactFramework, SmartPhone SDK, etc.

5. Removed from the registry everything that had to do with eVB, eVC,
"Windows CE", "Platman", "Visual Studio.NET"

5. Ran Microsoft RegClean to clean up the registry.

6. Rebooted the machine and reinstalled Visual Studio.NET 2003.

Hope this helps,
Johann Blake

Mobile solutions using GPS
www.closerworlds.com/engI solved this problem but didn't have the time to post what I found.

All I had to do is delete the OBJ and BIN folders from all projects in
the solution, then choose rebuild all. It worked then without even
restarting Visual Studio.NET itself

I hope this helps

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
I was having the same problem and you post help fixes it.

Thank you so much!

"Mohammed Banat" <mbanat@.e-sensejo.com> wrote in message
news:ukRrI8SRDHA.2196@.TK2MSFTNGP11.phx.gbl...
> I solved this problem but didn't have the time to post what I found.
> All I had to do is delete the OBJ and BIN folders from all projects in
> the solution, then choose rebuild all. It worked then without even
> restarting Visual Studio.NET itself
> I hope this helps
>
> *** Sent via Developersdex http://www.developersdex.com ***
> Don't just participate in USENET...get rewarded for it!

Happy to hear it worked.

I will be happier to learn that the next service release/service pack
will have this solved.

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
I was encountering this issue as well. I tried a lot of the
suggestions, but it came down to a project version issue. This is hard
to explain as it was hard to discover.

I have 3 projects. Project 1 is my asp.net application. Project 2 has
my base page. Project 3 has a lot of core classes used by both project
1 and 2. Project 2 and 3 are in the same solution. I built project 3
and copied the dll from the build directory to a central place where I
store my dlls. Later I made changes to project 2 and only copied the
dll from project 2 to the central location. Since project 2 and 3 are
in the same solution project 2 has a project reference to project 3.
Both of them have an AssemblyVersion of "1.0.*". Since the dlls from
project 2 and 3 were from different builds project 2 had a version
conflict.

The designer was the only thing that did not work. The application
still ran fine. All I had to do was make sure that I use the dlls from
the output (bin folder) of project 2 from the same build version. I
performed a lot of the above mentioned steps from removing the bin and
obj folders to deleting temp files. Getting the same versions of the
dlls was the step that finally resolved my issue and let me use the
designer again.