Re: VS 2005 - Beta testers - were there any?

Tech-Archive recommends: Fix windows errors by optimizing your registry

Are you saying that if you are starting a new project today, (which I am
[windows forms]) you would be better off with VS 2003 and .NET 1.1 then with
VS 2005 and .NET 2.0?


"Joe Mamma" <someone@xxxxxxxxxxxxx> wrote in message
news:%23N8w6MbiGHA.4276@xxxxxxxxxxxxxxxxxxxxxxx
Microsoft isnt lost, but they are focused on Vista and WinFX (and hopefuly
the disapearence of this hideous aspx model).

I strongly believe VS 2005 and Net 2.0 were just 'do something until Vista
and WinFX are ready and don't spend a lot of money on it'.

Think about this - Vista ships in January, how long do you think MS can
wait until a real visual studio that supports all of it's features comes
out? Plus they have been preveiwing Net 3.0 (LINQ & DLINQ in particular)
before 2.0 even RTMd.

I too am sorry I made the decision to start a couple of new projects in VS
2005 and I agree they either ignored beta test suggestions, or never gave
it to real developers - but I think the 'light at the end of the tunnel'
may be the next release and not that far away - fingers crossed.

J

"Rob R. Ainscough" <robains@xxxxxxxxxxx> wrote in message
news:%23iGCv1XiGHA.3780@xxxxxxxxxxxxxxxxxxxxxxx
No thanks -- but there lies the problem, those of us that are deep into
many large projects with real client $$$ on the line that push and push
the platform are not likely to have any time to report 100's even 1000's
of issues. And I believe this is exactly the problem I'm seeing in the
released VS 2005 -- it was Beta tested on a ad-hoc type basis with
developers that had time on their hands but no real scale -- where large
scale project testing was tossed in favor of smaller "focused" solutions
testing. It is also very apparent that large projects were NOT migrated
from VS 2003 to VS 2005 while in Beta -- the migration bugs/issues alone
are staggering.

It is as if Microsoft think that all developers using .NET platforms only
code "enterprise" component solutions with a few web service here and
there or just a handful of user control with a few web pages and toss in
a class library or two. It is as if they feel that a large solution
should not exist. As I proceed it is more likely that I'm going to move
to Java for web development, still retain my existing web services, and
go with C++ for all other functionality I need to build at a client
level.

My bottom line, it was my fault "believing" that VS2005 was the light at
the end of the tunnel and that migration from VS2003 would be easy and
all other issues with VS2003 would be resolved in VS2005. VS2005 does
have some great features, but if they don't work right or cause major
performance problems in large solutions, what's the point?? Since VS
2005 still requires me to use JavaScript to get some things done, I may
as well just go with full blown Java development. IMHO Microsoft are a
lost company right now and their stock would see to indicate the same.
From what I've used of the Vista beta I'm not seeing the a big revenue
generator -- I would guess that game development and XBOX 360 is what is
keeping MS alive (along with their huge cash reserve).

Rob.


"Andrew McDonald" <myrmecophagavir@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:O9frX2OiGHA.1000@xxxxxxxxxxxxxxxxxxxxxxx
"Rob R. Ainscough" <robains@xxxxxxxxxxx> wrote...
I'm finding more and more difficult to justify VS 2005 as my
development platform, I continue to run into more an more problems
especially on large scale projects. Some of the obvious issues:

You could probably even have got in on the beta yourself, I'd certainly
suggest it in the future if you've got a big dependence on the platform.
You can still report the issues on the bugtracker and they might get
fixed in the service packs:

http://lab.msdn.microsoft.com/productfeedback/

--
Andrew







.

Quantcast