- Service Pack 2 required to load Visual Studio 2005 Beta? Say it isn't so

  • Thread starter Thread starter -RG
  • Start date Start date
R

-RG

Just decided to load the VS 2005 beta 2 DVD and got a message on
install about SP2 required. Then abort. I really don't need or want
SP2 yet. Why would they need SP2? Is there a way around this?
 
hi,

what's wrong with SP2? at this point you should have it installed.

AFAIK there is no workaround it, you have to have it installed

cheers,
 
RG,

With SP2, there were new API calls introduced into the OS (there usually
is with new service packs). VS.NET 2005 most likely depends on a few of
those APIs being there, hence the dependency.

Hope this helps.
 
I don't see any new Win32 API's in SP2, am I missing something?

Willy.

Nicholas Paldino said:
RG,

With SP2, there were new API calls introduced into the OS (there
usually is with new service packs). VS.NET 2005 most likely depends on a
few of those APIs being there, hence the dependency.

Hope this helps.


--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

-RG said:
Just decided to load the VS 2005 beta 2 DVD and got a message on
install about SP2 required. Then abort. I really don't need or want
SP2 yet. Why would they need SP2? Is there a way around this?
Click to expand...
Click to expand...
 
We might have different definitions of what API is. They did add new
functions (bluetooth, firewall, for example) with this latest service pack
in the form of functions exported from a DLL, and I believe some new COM+
stuff (which is accessed through the appropriate interface).

Of course, if any of this is needed in VS.NET 2005, I don't know.
However, I wouldn't put it past them to just want to make sure that everyone
is up to date with their machines (much like the way they forced their JVM
down everyone's throats "what, I need the JVM to install SQL server?")


--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

Willy Denoyette said:
I don't see any new Win32 API's in SP2, am I missing something?

Willy.

Nicholas Paldino said:
RG,

With SP2, there were new API calls introduced into the OS (there
usually is with new service packs). VS.NET 2005 most likely depends on a
few of those APIs being there, hence the dependency.

Hope this helps.


--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

-RG said:
Just decided to load the VS 2005 beta 2 DVD and got a message on
install about SP2 required. Then abort. I really don't need or want
SP2 yet. Why would they need SP2? Is there a way around this?
Click to expand...
Click to expand...
Click to expand...
 
Right, when I'm talking about an "OS introduced APIs" I'm talking about the
"Windows API" or simply Win32/Win64 API, and as there are no new Win32 API's
introduced in XP SP2 this can't be the reason for this requirement. VS 2005
has (and should not have) IMO no specific requirements for one of the DLL's
you mention to be present, else, how would you explain it can be installed
on W2K SP4 and W2K3 who lack support for bluetooth, firewall etc...?
IMO it's because Microsoft's desktop base platform for VS2005 is XP SP2, and
it's a great "opportunity" for MS to (rightfully) force people to upgrade to
a more secure OS.

Willy.



Nicholas Paldino said:
We might have different definitions of what API is. They did add new
functions (bluetooth, firewall, for example) with this latest service pack
in the form of functions exported from a DLL, and I believe some new COM+
stuff (which is accessed through the appropriate interface).

Of course, if any of this is needed in VS.NET 2005, I don't know.
However, I wouldn't put it past them to just want to make sure that
everyone is up to date with their machines (much like the way they forced
their JVM down everyone's throats "what, I need the JVM to install SQL
server?")


--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

Willy Denoyette said:
I don't see any new Win32 API's in SP2, am I missing something?

Willy.

Nicholas Paldino said:
RG,

With SP2, there were new API calls introduced into the OS (there
usually is with new service packs). VS.NET 2005 most likely depends on
a few of those APIs being there, hence the dependency.

Hope this helps.


--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

Just decided to load the VS 2005 beta 2 DVD and got a message on
install about SP2 required. Then abort. I really don't need or want
SP2 yet. Why would they need SP2? Is there a way around this?
Click to expand...
Click to expand...
Click to expand...
 
hi,

what's wrong with SP2? at this point you should have it installed.

AFAIK there is no workaround it, you have to have it installed

cheers,
Click to expand...

As with most patches, it seems to have its own set of new bugs (to be
expected). However, the main reason is incompatibility with a wide
range of software. I see complaints about SP2 everywhere. I don't
recall a similar buzz about SP1 or any other non-XP service pack that
I can remember.

Granted, SP2 has been in the field long enough that issues should have
been resolved (my MS or by vendors of incompatible software).
However, I don't think that's the case yet.
 
(X'd to csharp, vc for crossplatform question below)

I suppose MS has to try to force users to go to their next platform,
but I think anyone who is serving as a beta development site could
figure out how to install a real firewall. Unless there were security
features that were integrated into the API, I still think it's awkward
to use this as leverage for SP2.

Has no one had any other issues with SP2? I'm reluctant to load the
beta, as google search turns up so many horror stories about SP2.

My main goal in this is to get a look at C++/CLI and try to port some
mixed C#/C++ code that was problematic with unmanaged extensions.
Does the *first* beta: 1) have support for C++/CLI? 2) require SP2?
 
_R said:
(X'd to csharp, vc for crossplatform question below)

I suppose MS has to try to force users to go to their next platform,
but I think anyone who is serving as a beta development site could
figure out how to install a real firewall. Unless there were security
features that were integrated into the API, I still think it's awkward
to use this as leverage for SP2.

Has no one had any other issues with SP2? I'm reluctant to load the
beta, as google search turns up so many horror stories about SP2.

My main goal in this is to get a look at C++/CLI and try to port some
mixed C#/C++ code that was problematic with unmanaged extensions.
Does the *first* beta: 1) have support for C++/CLI? 2) require SP2?
Click to expand...

I'm using SP2 since it's been in Beta and never had any major problem. You
will see these "error stories" whenever MS releases a SP, it has always been
like this since NT 3.1 and it will always stay like this.
C++/CLI is part of Beta2 (except for some minor missing bits), Beta1 had
some limited C++/CLI support and is IMO no longer available, anyway it's not
worth the trouble to try it now Beta2 is available.

Willy.
 
I'm using SP2 since it's been in Beta and never had any major problem. You
will see these "error stories" whenever MS releases a SP, it has always been
like this since NT 3.1 and it will always stay like this.
C++/CLI is part of Beta2 (except for some minor missing bits), Beta1 had
some limited C++/CLI support and is IMO no longer available, anyway it's not
worth the trouble to try it now Beta2 is available.

Willy.
Click to expand...

Thanks, Willy. I already have beta 1. Ordered it when it came out
but never loaded it. If support for C++/CLI is much more extensive in
beta 2, then I'll go with that.
 
_R said:
Thanks, Willy. I already have beta 1. Ordered it when it came out
but never loaded it. If support for C++/CLI is much more extensive in
beta 2, then I'll go with that.
Click to expand...

Well, it's actually getting better and better, the latest drop (the July
CTP, downloadable by MSDN Universal subscribers) also includes a version of
the long awaited STL.NET (named CLR.NET by now), just wait a few more weeks
and you'll probably be able to download the express version.

Willy.
 
Back
Top