the asp.net web forms designer

<rant>
Just wondering if it's just me, or is the 2003 asp.net web forms designer an
HTML-mangling, unstable, poorly written POS?
</rant>
Paulturn off the auto formatting options..
and yes, it is.
Curt Christianson
site: http://www.darkfalz.com
blog: http://blog.darkfalz.com
"PJ6" wrote:

> <rant>
> Just wondering if it's just me, or is the 2003 asp.net web forms designer
an
> HTML-mangling, unstable, poorly written POS?
> </rant>
> Paul
>
>
*yawn*
Then why not go back to using whatever non-MS product you're a fanboy of?
"PJ6" <nobody@dotnet.itags.org.nowhere.net> wrote in message
news:OFuwrTmrFHA.3352@dotnet.itags.org.TK2MSFTNGP14.phx.gbl...
> <rant>
> Just wondering if it's just me, or is the 2003 asp.net web forms designer
an
> HTML-mangling, unstable, poorly written POS?
> </rant>
> Paul
>
I'm totally new to web development. If you have a suggestion for an
alternative I'm all ears.
Paul
"Aidy" <sorry@dotnet.itags.org.noemail.zzz> wrote in message
news:elhnlrmrFHA.1684@dotnet.itags.org.TK2MSFTNGP14.phx.gbl...
> *yawn*
> Then why not go back to using whatever non-MS product you're a fanboy of?
> "PJ6" <nobody@dotnet.itags.org.nowhere.net> wrote in message
> news:OFuwrTmrFHA.3352@dotnet.itags.org.TK2MSFTNGP14.phx.gbl...
> an
>
VS.NET is not meant for you to really design professional pages in. It's
good for quick things - but most web designers use another product.
Then, the development for the code behind the page is done in VS.NET.
Sorry, but this is not news.
"PJ6" <nobody@dotnet.itags.org.nowhere.net> wrote in message
news:OFuwrTmrFHA.3352@dotnet.itags.org.TK2MSFTNGP14.phx.gbl...
> <rant>
> Just wondering if it's just me, or is the 2003 asp.net web forms designer
> an HTML-mangling, unstable, poorly written POS?
> </rant>
> Paul
>

the asp.net web forms designer

<rant>
Just wondering if it's just me, or is the 2003 asp.net web forms designer an
HTML-mangling, unstable, poorly written POS?
</rant
Paulturn off the auto formatting options..
and yes, it is.

--
Curt Christianson
site: http://www.darkfalz.com
blog: http://blog.darkfalz.com

"PJ6" wrote:

> <rant>
> Just wondering if it's just me, or is the 2003 asp.net web forms designer an
> HTML-mangling, unstable, poorly written POS?
> </rant>
> Paul
>
*yawn*

Then why not go back to using whatever non-MS product you're a fanboy of?

"PJ6" <nobody@dotnet.itags.org.nowhere.net> wrote in message
news:OFuwrTmrFHA.3352@dotnet.itags.org.TK2MSFTNGP14.phx.gbl...
> <rant>
> Just wondering if it's just me, or is the 2003 asp.net web forms designer
an
> HTML-mangling, unstable, poorly written POS?
> </rant>
> Paul
I'm totally new to web development. If you have a suggestion for an
alternative I'm all ears.

Paul

"Aidy" <sorry@dotnet.itags.org.noemail.zzz> wrote in message
news:elhnlrmrFHA.1684@dotnet.itags.org.TK2MSFTNGP14.phx.gbl...
> *yawn*
> Then why not go back to using whatever non-MS product you're a fanboy of?
> "PJ6" <nobody@dotnet.itags.org.nowhere.net> wrote in message
> news:OFuwrTmrFHA.3352@dotnet.itags.org.TK2MSFTNGP14.phx.gbl...
>> <rant>
>> Just wondering if it's just me, or is the 2003 asp.net web forms designer
> an
>> HTML-mangling, unstable, poorly written POS?
>> </rant>
>>
>> Paul
>>
>>
VS.NET is not meant for you to really design professional pages in. It's
good for quick things - but most web designers use another product.
Then, the development for the code behind the page is done in VS.NET.

Sorry, but this is not news.

"PJ6" <nobody@dotnet.itags.org.nowhere.net> wrote in message
news:OFuwrTmrFHA.3352@dotnet.itags.org.TK2MSFTNGP14.phx.gbl...
> <rant>
> Just wondering if it's just me, or is the 2003 asp.net web forms designer
> an HTML-mangling, unstable, poorly written POS?
> </rant>
> Paul

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.

The file could not be loaded into the Web Forms designer

I'm having some problem with my Visual Studio.NET 2003 (.NET 1.1 SP1)
install. I am unable to use the web forms designer with any aspx file
whose
form class inherits from a base class. I'm implementing the page
controller
design pattern and everything has been working fine until now. My form
inherits from a base class called CampusNET.CampusPage. The class
exists, is
included in the project and compiles just fine. If I replace the base
class
for my form with the standard System.Web.UI.Page, the designer can open
the
form without any problems, but as soon as I try to inherit from my base
class, it breaks down. I've tried it with an empty base class with only
the
Page_Load method, but the problem remains.

The base class is not abstract so that's not the issue. Neither is the
problem related to the registry entry that leads to the "Illegal
character
in path" error. The full error message looks like this:

"The file could not be loaded into the Web Forms designer. Please
correct
the following error and then try loading it again:

The designer could not be shown for this file because none of the
classes
within can be designed. The designer inspected the following classes in
the
file:

MenuTest -- The base class 'CampusNET.CampusPage' could not be loaded.

Ensure the assembly has been referenced or built if it is part of the
project.

Make sure all of the classes used in the page are build or referenced
in the
project. Click Help for more information."

Has anyone encountered this problem before? I really need to get this
fixed
as soon as possible.

Regards
/CThis is a known issue. I'm pretty certain that it's fixed in VS2005.
I've had something similar with my own base classes... probably a simpler
situation than yours. Mine rears it's head the first time you get the source
code from source control, before you build your project. My project also
contains the base class. It seems as if the designer needs the compiled
version of the base class present - so my fix is to build the project so the
base class gets fixed and all seems to work OK

Hope this helps

Richard MCSD .NET

"crusell@.gmail.com" wrote:

> I'm having some problem with my Visual Studio.NET 2003 (.NET 1.1 SP1)
> install. I am unable to use the web forms designer with any aspx file
> whose
> form class inherits from a base class. I'm implementing the page
> controller
> design pattern and everything has been working fine until now. My form
> inherits from a base class called CampusNET.CampusPage. The class
> exists, is
> included in the project and compiles just fine. If I replace the base
> class
> for my form with the standard System.Web.UI.Page, the designer can open
> the
> form without any problems, but as soon as I try to inherit from my base
> class, it breaks down. I've tried it with an empty base class with only
> the
> Page_Load method, but the problem remains.
> The base class is not abstract so that's not the issue. Neither is the
> problem related to the registry entry that leads to the "Illegal
> character
> in path" error. The full error message looks like this:
> "The file could not be loaded into the Web Forms designer. Please
> correct
> the following error and then try loading it again:
> The designer could not be shown for this file because none of the
> classes
> within can be designed. The designer inspected the following classes in
> the
> file:
> MenuTest -- The base class 'CampusNET.CampusPage' could not be loaded.
> Ensure the assembly has been referenced or built if it is part of the
> project.
> Make sure all of the classes used in the page are build or referenced
> in the
> project. Click Help for more information."
> Has anyone encountered this problem before? I really need to get this
> fixed
> as soon as possible.
> Regards
> /C
>

The file could not be loaded into the Web Forms designer

I'm having some problem with my Visual Studio.NET 2003 (.NET 1.1 SP1)
install. I am unable to use the web forms designer with any aspx file
whose
form class inherits from a base class. I'm implementing the page
controller
design pattern and everything has been working fine until now. My form
inherits from a base class called CampusNET.CampusPage. The class
exists, is
included in the project and compiles just fine. If I replace the base
class
for my form with the standard System.Web.UI.Page, the designer can open
the
form without any problems, but as soon as I try to inherit from my base
class, it breaks down. I've tried it with an empty base class with only
the
Page_Load method, but the problem remains.
The base class is not abstract so that's not the issue. Neither is the
problem related to the registry entry that leads to the "Illegal
character
in path" error. The full error message looks like this:
"The file could not be loaded into the Web Forms designer. Please
correct
the following error and then try loading it again:
The designer could not be shown for this file because none of the
classes
within can be designed. The designer inspected the following classes in
the
file:
MenuTest -- The base class 'CampusNET.CampusPage' could not be loaded.
Ensure the assembly has been referenced or built if it is part of the
project.
Make sure all of the classes used in the page are build or referenced
in the
project. Click Help for more information."
Has anyone encountered this problem before? I really need to get this
fixed
as soon as possible.
Regards
/CThis is a known issue. I'm pretty certain that it's fixed in VS2005.
I've had something similar with my own base classes... probably a simpler
situation than yours. Mine rears it's head the first time you get the sourc
e
code from source control, before you build your project. My project also
contains the base class. It seems as if the designer needs the compiled
version of the base class present - so my fix is to build the project so the
base class gets fixed and all seems to work OK
Hope this helps
Richard MCSD .NET
"crusell@.gmail.com" wrote:

> I'm having some problem with my Visual Studio.NET 2003 (.NET 1.1 SP1)
> install. I am unable to use the web forms designer with any aspx file
> whose
> form class inherits from a base class. I'm implementing the page
> controller
> design pattern and everything has been working fine until now. My form
> inherits from a base class called CampusNET.CampusPage. The class
> exists, is
> included in the project and compiles just fine. If I replace the base
> class
> for my form with the standard System.Web.UI.Page, the designer can open
> the
> form without any problems, but as soon as I try to inherit from my base
> class, it breaks down. I've tried it with an empty base class with only
> the
> Page_Load method, but the problem remains.
> The base class is not abstract so that's not the issue. Neither is the
> problem related to the registry entry that leads to the "Illegal
> character
> in path" error. The full error message looks like this:
> "The file could not be loaded into the Web Forms designer. Please
> correct
> the following error and then try loading it again:
> The designer could not be shown for this file because none of the
> classes
> within can be designed. The designer inspected the following classes in
> the
> file:
> MenuTest -- The base class 'CampusNET.CampusPage' could not be loaded.
> Ensure the assembly has been referenced or built if it is part of the
> project.
> Make sure all of the classes used in the page are build or referenced
> in the
> project. Click Help for more information."
> Has anyone encountered this problem before? I really need to get this
> fixed
> as soon as possible.
> Regards
> /C
>