VS 2005 SP1??? where?

  • Thread starter Thread starter Rob R. Ainscough
  • Start date Start date
Rob said:
Seeing as there is only 19 days left in Q3 this looks sorta like it isn't
going to happen...
Click to expand...

Well, they've got until the end of September. It could still happen!

Chris <-------------- Not holding his breath
 
Rob said:
Trying to get more info on this, anyone??

http://msdn.microsoft.com/vstudio/support/servicing/sp1_vs05/default.a
spx

Has anyone seen "a more detailed schedule of external interim
milestones...will be posted when it has been finalized."?

Seeing as there is only 19 days left in Q3 this looks sorta like it
isn't going to happen...
Click to expand...

It's not even in beta, so I'd say: forget it. My guess it's not going
to be released before Q1 2007, IF ever.

FB

--
------------------------------------------------------------------------
Lead developer of LLBLGen Pro, the productive O/R mapper for .NET
LLBLGen Pro website: http://www.llblgen.com
My .NET blog: http://weblogs.asp.net/fbouma
Microsoft MVP (C#)
------------------------------------------------------------------------
 
Ok thanks -- do you have any sources to confirm no SP1 til Q1'07 or never?
We're just waiting for my "go" or "no go" decision on whether we migrate all
our tools/products to a different development platform -- going with VS 2005
is beyond embarrassing for me at this point.

Rob.
 
Rob said:
Ok thanks -- do you have any sources to confirm no SP1 til Q1'07 or
never? We're just waiting for my "go" or "no go" decision on whether
we migrate all our tools/products to a different development platform
-- going with VS 2005 is beyond embarrassing for me at this point.
Click to expand...

I have no exact date for you. Only that SP1 for .NET 2.0 is scheduled
for Q1 2007 and that there's no SP1 in sight for 2005, as it first has
to get into beta.

Frans
Rob.
Click to expand...


--
------------------------------------------------------------------------
Lead developer of LLBLGen Pro, the productive O/R mapper for .NET
LLBLGen Pro website: http://www.llblgen.com
My .NET blog: http://weblogs.asp.net/fbouma
Microsoft MVP (C#)
------------------------------------------------------------------------
 
After some more digging and phone calls, it appears you are correct, no SP1
for VS 2005 this year and the SP1 for .NET 2.0 is due out about the same
time Vista goes final.

Tis unfortunate, VS 2005 is feature packed with potential -- too bad the
features have some pretty significant problems that aren't going to be fixed
any time soon.

And so begins the un-migration. Maybe I'll have a job after this or not,
who knows, but it sure is the last time I put "faith" in Microsoft.

Rob.
 
After some more digging and phone calls, it appears you are correct,
no SP1 for VS 2005 this year and the SP1 for .NET 2.0 is due out
about the same time Vista goes final.

Tis unfortunate, VS 2005 is feature packed with potential -- too bad
the features have some pretty significant problems that aren't going
to be fixed any time soon.
Click to expand...

Very unfortunate, indeed. Considering how highly anticipated VS 2005
was at the time and how spotty its stability had turned out, you'd
think they'll be past SP1 and working toward SP2 by now. Microsoft
needs to realize that a lot of .NET shops with existing 1.1 projects
*know* about VS 2005 stability issues and sit on the fence waiting for
SP1 to show up. No SP1 no sale, I'm afraid.
--
Sergey Mishkovskiy
http://www.usysware.com/dpack/ - DPack - free VS.NET add-ons
http://www.usysware.com/blog/

My recent MSDN article:
"Code & Seek: Bring Windows Desktop Search Into Visual Studio With Our
Cool Add-In"
http://msdn.microsoft.com/msdnmag/issues/06/07/CodeAndSeek/
 
Very unfortunate, indeed. Considering how highly anticipated VS 2005 was
at the time and how spotty its stability had turned out, you'd think
they'll be past SP1 and working toward SP2 by now.
Click to expand...

I agree 100%.

There are a number of VS 2005 features that don't work right, and have made
things very difficult to use.

The one that really ticks me off the most is the inability of the WinForms
designer to work right with custom controls and visual inheritence. This has
made Windows Forms development practically unusable (yes, I do mean that)
for anything of signifigant complexity. We've had to completly abandon forms
inheritence and user controls as a result of this, and have paid an ugly
price in doing so.
 
Rob said:
After some more digging and phone calls, it appears you are correct,
no SP1 for VS 2005 this year and the SP1 for .NET 2.0 is due out
about the same time Vista goes final.

Tis unfortunate, VS 2005 is feature packed with potential -- too bad
the features have some pretty significant problems that aren't going
to be fixed any time soon.
Click to expand...

I'm sure I'm not doing the same kind of development as alot of people
here (more library work, less forms oriented work), but I have to say
that it's fairly stable for me, even with large projects. But as said,
I don't spend most of my time writing GUI-tiers and when I have to
write GUI code, I have to agree with you that it often takes more time
than when you've to write the same amount of code in library classes.

So could you elaborate a bit what makes it impossible to use VS.NET
2005 for you?
And so begins the un-migration. Maybe I'll have a job after this or
not, who knows, but it sure is the last time I put "faith" in
Microsoft.
Click to expand...

As your job is on the line, you could ask Microsoft to fix the
problems you have for you. I'm not sure if your employer is a large
company, but as much as I hate it, big companies have a huge impact on
what MS does. So if your employer wants to get things fixed / changed
so they can proceed and won't switch to java instead, I'd give it a
shot and ask MS to help you with the migration.

If you want I could mail some people inside MS and ask them if they
want to escalate this thread internally? It won't change things in the
very short term, but it might give you more confidence in having a job
later in the year.

Frans
Rob.


whether >> we migrate all our tools/products to a different
development platform >> -- going with VS 2005 is beyond embarrassing
for me at this point.
Click to expand...


--
------------------------------------------------------------------------
Lead developer of LLBLGen Pro, the productive O/R mapper for .NET
LLBLGen Pro website: http://www.llblgen.com
My .NET blog: http://weblogs.asp.net/fbouma
Microsoft MVP (C#)
------------------------------------------------------------------------
 
We would like to move our group's main project, 300K+ lines of C++/MFC code
to VS 2005. I migrated our product to test VS 2005 and the instability made
it unuseable.

We'd love to upgrade for the many excellent features but there's no way we
can move to an IDE that literally crashes several times a day and often
becomes posessed by Intellisense hogging 100% CPU for several minutes at a
time.

We're sitting around waiting for SP1 due out Q3 of 2006 (just a few days) as
promised by Microsoft at
msdn.microsoft.com/vstudio/support/servicing/sp1_vs05/default.aspx.

Is SP1 coming or not? Customers (including us) are sitting around waiting to
test SP1 to see if it corrects stability and other issues so that they can
migrate to VS 2005.

Can someone please just give us a definitive answer on this? The future of
our products are at stake.
--
Thanks,

Dwight
 
To add my 2 cents... / thoughts

I am learning vb.net and a "single user" and am pretty happy with it.
I guess it all depends on how complex your programs become and how fast you
need the bugs fixed.

I'm now at the point where I will be buying a 2005 prof version in the next
2 weeks.

I am self employed, and this is the first time I am choosing a Microsoft
product to start writing my new apps in slowly.
Currently I'm at the "basic / very basic" stage, but I just hope I don't run
into the same issues you are having.

From what I am reading from your posts, waiting and waiting and waiting on a
fix could throw me a good monkey wrench too.

Have you had issues with 2003 like this before or is this thier first
"patch" that is late?

Needless to say, Im trying to keep my costs down so if any of you are
switching and are dropping 2005 prof. and have a spare copy to sell, let me
know. :-) { I didn't enjoy writing that ( on your misfortunes ) but I
did give myself a small budget to slowly learn vb.net and slowly switch to
it ) - so I do apologize for it.


Miro
 
Back
Top