[quoted text, click to view] > Thanks for the response. It looks like I can upgrade to
> the pro version for around $500 but the Pro subscription
> is over $1000. We are also IT people so we have all the
> latest desktop and server OS's. Sounds like its an annual
> cost too. Not sure I see the benefit at this point.
Well, if you're getting an upgrade price, yes, it might be more expensive to
get a subscription. If you already have all the dev tools you need (SQL
Server, BizTalk, Virtual PC, etc.) then there might not be any point. It's
an annual subscription, but you aren't required to renew. The subscription
also gives you new software (such as VS2005) as soon as it's released.
[quoted text, click to view] > Regaring the actual upgrade process. Do you know if I
> will be required to instal VS6 first then upgrade? Or
> will the VS.Net install just prompt me for the CD to
> prove I own it? I want to avoid install VS6 if I can?
As far as the actual process, I couldn't find any information.
[quoted text, click to view] > Last question: I've seen where the .NET version of studio
> is supposed to improve on the way you develop web apps.
> My experience was to use Notepad to build ASP pages. Its
> a very lame approach to programming and offers no real
> way to debug, in my opinion. Does VS.NET resolve this
> issue and offer a VB style debugger for debugging ASP or
> ASP.net apps. Am I still limited to writing in Notepad?
ASP and ASP.NET apps are debuggable in VS.NET. They were also debuggable
with Visual Studio 6 (Visual Interdev). Please put notepad down :).
-mike
MVP
[quoted text, click to view] >
>
>>-----Original Message-----
>>Well, considering the difference is $1000+ between
> Standard and Pro, and
>>another $1000+ for enterprise, go with whatever you can
> afford :). I
>>personally can't work without Enterprise (the data
> tools). Here's a
>>comparison chart:
>>
http://msdn.microsoft.com/vstudio/howtobuy/choosing.aspx >>
>>If you decide to get Pro or Enterprise, *don't buy
> Visual Studio directly*!.
>>Get an MSDN subscription. It's almost the same price,
> except you get MUCH,
>>MUCH, more (all their servers, OSes, other dev products,
> etc.), inc. some
>>free support issues (They cost like $200 each).
>>
>>
http://msdn.microsoft.com/subscriptions/ >>
>>-mike
>>MVP
>>
>>"MB" <anonymous@discussions.microsoft.com> wrote in
> message
>>news:1c3ac01c421d7$bf650350$a401280a@phx.gbl...
>>>I have been using Visual Studio 6 Professional for some
>>> time now. However, I mainly use the VB and InterDev
>>> components. I haven't had much of a need for the other
>>> components(VFP, etc.) I'd like to upgrade to Visual
>>> Studio.NET 2003 but wasn't sure if I needed this full
>>> blown version. Maybe VB.net would be sufficient? My
> main
>>> interest at this point is to develop Windows
> applications
>>> as well as ASP.net applications. Will VB.net be enough
> or
>>> should I spring for the Pro version of VS.net? Does
>>> ASP.net development offer a VB style development
>>> environment or am I still stuck using Notepad to
> develop
>>> ASP webs?
>>>
>>> Also, I planned on installing on a new Win2003 Server.
> I
>>> have a full version of VS6 and would like to only
>>> purchase the VS.net upgrade instead of the full
> version.
>>> Will I be required to install VS6 first then upgrade
> it?
>>> Or will the VS.net install just ask for the CD to
> prove I
>>> have it. I would like to avoid installing VS6 on the
> new
>>> machine if I can avoid it.
>>>
>>> Thanks for any help you can provide.
>>>
>>> -mark
>>>
>>
>>.
>>
[quoted text, click to view] "MB" <anonymous@discussions.microsoft.com> wrote in message
news:1c74301c4223a$89855240$a501280a@phx.gbl...
> Regaring the actual upgrade process. Do you know if I
> will be required to instal VS6 first then upgrade? Or
> will the VS.Net install just prompt me for the CD to
> prove I own it? I want to avoid install VS6 if I can?
VS6, VS.NET, and VS\.NET 2003 will all peacefully coexist on one system.
The only gotcha is that VS.NET and VS.NET 2003 share the same extensions,
but incompatible file formats, so VS.NET 2003 becomes the default.
[quoted text, click to view] > Last question: I've seen where the .NET version of studio
> is supposed to improve on the way you develop web apps.
> My experience was to use Notepad to build ASP pages. Its
> a very lame approach to programming and offers no real
> way to debug, in my opinion. Does VS.NET resolve this
> issue and offer a VB style debugger for debugging ASP or
> ASP.net apps. Am I still limited to writing in Notepad?
It does, though I don't know how good it is. I did web/dB yuck with VS 6,
and I don't ever want to do that again with any tool.
Phil
--
Philip D. Barila Windows DDK MVP
Seagate Technology, LLC
(720) 684-1842
As if I need to say it: Not speaking for Seagate.
E-mail address is pointed at a domain squatter. Use reply-to instead.