G
Guest
I have VS.Net 2003 and .Net framework 1.1..
How can i get started with ASP.NET 2.0?
How can i get started with ASP.NET 2.0?
K
Karl Seguin
You can't with VS.Net 2003...
To get started download the Visual Web Developer Express Edition 2005:
http://lab.msdn.microsoft.com/express/vwd/default.aspx
Karl
To get started download the Visual Web Developer Express Edition 2005:
http://lab.msdn.microsoft.com/express/vwd/default.aspx
Karl
G
Guest
Karl thx for the prompt reply.
But i don't want to use "Visual Web Developer Express Edition 2005"
I want to use VS.Net 2003!
thx
But i don't want to use "Visual Web Developer Express Edition 2005"
I want to use VS.Net 2003!
thx
J
Juan T. Llibre
VS.NET 2003 works with the .NET Framework 1.1.
You can't use it to develop ASP.NET 2.0 applications.
To get started with ASP.NET 2.0, download VWD 2005:.
It won't ruin your VS.NET 2003 setup.
Juan T. Llibre
ASP.NET MVP
===========
You can't use it to develop ASP.NET 2.0 applications.
To get started with ASP.NET 2.0, download VWD 2005:.
It won't ruin your VS.NET 2003 setup.
Juan T. Llibre
ASP.NET MVP
===========
S
Steve C. Orr [MVP, MCSD]
Juan, it seems a bit cavalier for you to claim that this beta software won't
screw up his VS.NET 2003 installation.
That's exactly what happened with one of the beta builds I installed.
I suggest people don't install the VS2005 beta on an important production
machine. Use a spare computer, or use a Virtual PC.
screw up his VS.NET 2003 installation.
That's exactly what happened with one of the beta builds I installed.
I suggest people don't install the VS2005 beta on an important production
machine. Use a spare computer, or use a Virtual PC.
P
Philip Q [MVP]
Juan T. Llibre said:
On the contrary, installing VS.NET 2005 stopped VS.NET 2003 from being able
to start the debugger on my machine.
?
=?ISO-8859-1?Q?=22Anders_Nor=E5s_=5BMCAD=5D=22?=
The current VS2005 betas cannot be installed on a production machine asSteve said:
they don't come with "go live" licences.
Anders Norås
http://dotnetjunkies.com/weblog/anoras/
K
Karl Seguin
Just to add my $0.02 to a topic which doesn't need it. I have both running
fine on my development machine, but I agree that it wouldn't be wise to put
it on an important machine.
Karl
fine on my development machine, but I agree that it wouldn't be wise to put
it on an important machine.
Karl
J
Juan T. Llibre
re:
Betas should never be installed on production machines.
That's a given, yes.
I currently have VS.NET 2002, VS.NET 2003 & VS2005
all running in peace with each other in my development box,
without taking any special precautions.
I understand, though, that removing VS2005 could cause
some problems for the other two, although there's ways
to avoid those problems.
Using a Virtual Machine ( like Virtual PC or VMWare )
reduces the risks involved to practically zero.
Juan T. Llibre
ASP.NET MVP
===========
Betas should never be installed on production machines.
That's a given, yes.
I currently have VS.NET 2002, VS.NET 2003 & VS2005
all running in peace with each other in my development box,
without taking any special precautions.
I understand, though, that removing VS2005 could cause
some problems for the other two, although there's ways
to avoid those problems.
Using a Virtual Machine ( like Virtual PC or VMWare )
reduces the risks involved to practically zero.
Juan T. Llibre
ASP.NET MVP
===========
J
Juan T. Llibre
That's not exactly ruining the VS 2003 setup, Philip, is it ?
Were you able to fix it ? If so, how ?
Our fellow MVP Peter Bromberg reported that there
"appear to be no problem with existing version of
VS.NET 2003 residing on the same machine" :
http://www.eggheadcafe.com/articles/20040702.asp
Peter van Ooijen reports a minor problem, but shows how he fixed it.
http://dotnetjunkies.com/WebLog/petergekko/archive/2003/11/04/3150.aspx
I have not seen many reports of problems.
Using a VM ( like Virtual PC or VMWare )
reduces the risks and problems to zero.
Juan T. Llibre
ASP.NET MVP
===========
Were you able to fix it ? If so, how ?
Our fellow MVP Peter Bromberg reported that there
"appear to be no problem with existing version of
VS.NET 2003 residing on the same machine" :
http://www.eggheadcafe.com/articles/20040702.asp
Peter van Ooijen reports a minor problem, but shows how he fixed it.
http://dotnetjunkies.com/WebLog/petergekko/archive/2003/11/04/3150.aspx
I have not seen many reports of problems.
Using a VM ( like Virtual PC or VMWare )
reduces the risks and problems to zero.
Juan T. Llibre
ASP.NET MVP
===========
P
Philip Q [MVP]
Juan T. Llibre said:
I don't know about you, but I tend to debug a lot.
I fixed it when the VS.NET 2005 November CTP installer crapped out and I
uninstalled the whole thing.
However, Beta software is, as always, very unpredictable - and I always seem
to be the person stuck with the weird case that nobody can figure out.
J
Juan T. Llibre
re:
heh, heh...
Been there, done that.
Juan T. Llibre
ASP.NET MVP
===========
heh, heh...
Been there, done that.
Juan T. Llibre
ASP.NET MVP
===========
C
clintonG
I concur with Steve who by the way now has an ugly hair cut %-)
--
<%= Clinton Gallagher
METROmilwaukee "Regional Information Services"
NET csgallagher AT metromilwaukee.com
URL http://clintongallagher.metromilwaukee.com/
--
<%= Clinton Gallagher
METROmilwaukee "Regional Information Services"
NET csgallagher AT metromilwaukee.com
URL http://clintongallagher.metromilwaukee.com/
C
clintonG
Only once instance of the debugger will run on a machine (sucks) noting I
discovered this while running two instances of VSN2003 while attempting to
use the debugger(s) while converting a VB.NET application to a C#
application.
--
<%= Clinton Gallagher
METROmilwaukee "Regional Information Services"
NET csgallagher AT metromilwaukee.com
URL http://clintongallagher.metromilwaukee.com/
discovered this while running two instances of VSN2003 while attempting to
use the debugger(s) while converting a VB.NET application to a C#
application.
--
<%= Clinton Gallagher
METROmilwaukee "Regional Information Services"
NET csgallagher AT metromilwaukee.com
URL http://clintongallagher.metromilwaukee.com/
G
Guest
I found that in my existing VS.NET 2003 web apps, that IIS was set to use
version 2 of the framework. Go to Internet Services Manager, view properties
for the virtual directory on which you're trying to debug in VS.NET 2003, go
to ASP.NET tab, and make sure the correct version (probably 1.1) of the
framework is selected. That fixed it for me.
Todd
version 2 of the framework. Go to Internet Services Manager, view properties
for the virtual directory on which you're trying to debug in VS.NET 2003, go
to ASP.NET tab, and make sure the correct version (probably 1.1) of the
framework is selected. That fixed it for me.
Todd
J
Juan T. Llibre
Yup...
That's very common, and that's where Denis Bauer's
fantastic little app "ASP.NET Version Switcher" can
be a real life and time saver :
http://www.denisbauer.com/NETTools/ASPNETVersionSwitcher.aspx
Switching between .NET Framework versions
is a snap with it, as you don't need to open each
app individually in the IIS Manager, when switching
ASP.NET apps from version to version.
Just click the desired app, select the ASP.NET version wanted,
and click the "Switch .Net Framework Version" button!
Denis should get a statue made of him... ;-)
Juan T. Llibre
ASP.NET MVP
===========
That's very common, and that's where Denis Bauer's
fantastic little app "ASP.NET Version Switcher" can
be a real life and time saver :
http://www.denisbauer.com/NETTools/ASPNETVersionSwitcher.aspx
Switching between .NET Framework versions
is a snap with it, as you don't need to open each
app individually in the IIS Manager, when switching
ASP.NET apps from version to version.
Just click the desired app, select the ASP.NET version wanted,
and click the "Switch .Net Framework Version" button!
Denis should get a statue made of him... ;-)
Juan T. Llibre
ASP.NET MVP
===========
J
Juan T. Llibre
re:
Steve,
You might be interested in Kathy Tamanaha's opinion on
this issue, in microsoft.private.whidbey.setup.visual_studio :
---000---
VS2005 and VS2003 (as well as VS2002) all work Side By Side
on the same machine. Uninstalling one version should not affect the
functionality of the still installed versions on the machine.
Hope this helps,
Kathy Tamanaha
Visual Basic .NET Testing
Microsoft Corp.
---000---
Do you think her attitude is "cavalier", too ?
Juan T. Llibre
ASP.NET MVP
===========
Steve,
You might be interested in Kathy Tamanaha's opinion on
this issue, in microsoft.private.whidbey.setup.visual_studio :
---000---
VS2005 and VS2003 (as well as VS2002) all work Side By Side
on the same machine. Uninstalling one version should not affect the
functionality of the still installed versions on the machine.
Hope this helps,
Kathy Tamanaha
Visual Basic .NET Testing
Microsoft Corp.
---000---
Do you think her attitude is "cavalier", too ?
Juan T. Llibre
ASP.NET MVP
===========