Thanks for the article and feedback - all. Another year before I can get a
fix to some of these incredibly time wasting bugs! I can't believe it!
An even more annoying problem that has come up recently in our project is
really causing us a lot of pain. We have subdivided our code into 3 main
assemblies. The solution contains each project, and there are dependencies
setup between them to set the compile order. When switching between Debug
and Release, the project becomes corrupt, and about once per day I have to
do one or more of the following to get it going again:
1. Close and reopen Visual Studio
2. Stop the aspnet_wp.exe process
3. Delete all the DLL references and readd them to the project
4. Delete the IIS Virtual Directory, recreate it. This is a major pain
because I have about 20 file mappings that have to be recreated each time I
do this.
This is not isolated to my machine, but happens on our other developers
machines in our company.
The other problem that is really driving us crazy is the instability in the
compiler. All of our developers have this too - the compiler locks up and
goes South several times a day. It just looses it's mind and totally stops
responding, and the browser locks up, and all control is lost inside VS.
That MS wouldn't spend the time to correct these problems in the compiler is
absolutely unacceptable considering how much money we are sending to MS each
year for our MSDN subscriptions!!!!
http://www.informationweek.com/story/showArticle.jhtml?articleID=18312194
If you guys have any influence as a MVP please let MS know that lots of
current (paid up) developers are tired of waiting for the promissed land.
Maybe they should fix what they have first.
Lloyd Sheen
Alvin Bruney said:
these problems are addressed in whidbey
--
Regards,
Alvin Bruney [ASP.NET MVP]
Got tidbits? Get it here...
http://tinyurl.com/3he3b
Joe,
I agree with you fully. This newgroup is full of complaints but it seems
that all MS people keep telling us to wait until the next release. Well
MS
has constantly put this back. So how suffers. The developers who are
supposed to help MS in creating apps that will bring customers to their
products.
Would it not be in their interest to fix these problems??
Lloyd Sheen
Not only does it re-format the HTML (randomly) it also drops code like
runat="server" !!
Every time I edit a page and switch between HTML and design view I have
to
check this in my <Head> tag.
Both of these bugs are a real pain.
--
Joe Fallon
message
If you are using ASP.NET the stupid IDE will reformat the HTML etc.
This
constitutes a change as far as the IDE is concerned and marks
the
page
as
changed.
No way around it that I know. Perhaps some day MS will come up with
an
IDE
that can figure out that opening a file does not constitute an
agreement
to
reformat and do other behind the scenes changes to information that
developers have spent precious time developing.
But not to worry, someone will say "wait until next release". I think
you
are probably amoung those who would like an update to fix all the
little
problems that make this IDE a pain in the butt.
Lloyd Sheen
Why does Visual Studio sometimes mark my .ascx files as
"changed"
as
soon
as
I open them, and before I've even touched the file in any way?
Since
I
only
want
to save files that are changed so that the file dates are reflective
of
files that were actually changed for code management purposes, this
is
quite
critical to me. Does anyone know how to fix or workaround
this
bug
.