asp.net sites resulting in the fact that you can no longer debug your
asp.net v1.1.4... applications with visual studio.net 2003.
I have spent some time wondering why i could no longer debug my
existing apps. right after my instalation completed and at my big surprise,
IIS has "configured" them to use
asp.net 2.
When i manually corrected this, things started working again.
I wondwer how many other untold stories there are out there about this
issue.
Thanks
JBYou can set the version for the roots that are still 1.1, using
aspnet_regiis:
http://support.microsoft.com/defaul...kb;en-us;816782
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
************************************************
Think Outside the Box!
************************************************
"bredal Jensen" <bred.jen@.mimosa.com> wrote in message
news:Ogsx6I2YEHA.3012@.tk2msftngp13.phx.gbl...
> It will go ahead and configure IIS to use asp.net 2.0 for your existing
> asp.net sites resulting in the fact that you can no longer debug your
> asp.net v1.1.4... applications with visual studio.net 2003.
> I have spent some time wondering why i could no longer debug my
> existing apps. right after my instalation completed and at my big
surprise,
> IIS has "configured" them to use
> asp.net 2.
> When i manually corrected this, things started working again.
> I wondwer how many other untold stories there are out there about this
> issue.
>
> Thanks
>
> JB
Thanks for this warning. I haevn't installed my Epress stuff yet, and now I
will do so on VMWare or VPC.
"bredal Jensen" <bred.jen@.mimosa.com> wrote in message
news:Ogsx6I2YEHA.3012@.tk2msftngp13.phx.gbl...
> It will go ahead and configure IIS to use asp.net 2.0 for your existing
> asp.net sites resulting in the fact that you can no longer debug your
> asp.net v1.1.4... applications with visual studio.net 2003.
> I have spent some time wondering why i could no longer debug my
> existing apps. right after my instalation completed and at my big
surprise,
> IIS has "configured" them to use
> asp.net 2.
> When i manually corrected this, things started working again.
> I wondwer how many other untold stories there are out there about this
> issue.
>
> Thanks
>
> JB
A good idea always. Never install betaware on a production machine (machine
you cannot afford to take time to rebuild).
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
************************************************
Think Outside the Box!
************************************************
"middletree" <middletree@.htomail.com> wrote in message
news:%23qJDla2YEHA.556@.tk2msftngp13.phx.gbl...
> Thanks for this warning. I haevn't installed my Epress stuff yet, and now
I
> will do so on VMWare or VPC.
>
> "bredal Jensen" <bred.jen@.mimosa.com> wrote in message
> news:Ogsx6I2YEHA.3012@.tk2msftngp13.phx.gbl...
> > It will go ahead and configure IIS to use asp.net 2.0 for your existing
> > asp.net sites resulting in the fact that you can no longer debug your
> > asp.net v1.1.4... applications with visual studio.net 2003.
> > I have spent some time wondering why i could no longer debug my
> > existing apps. right after my instalation completed and at my big
> surprise,
> > IIS has "configured" them to use
> > asp.net 2.
> > When i manually corrected this, things started working again.
> > I wondwer how many other untold stories there are out there about this
> > issue.
> > Thanks
> > JB
You can set the version for the roots that are still 1.1, using
aspnet_regiis:
http://support.microsoft.com/defaul...kb;en-us;816782
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
************************************************
Think Outside the Box!
************************************************
"bredal Jensen" <bred.jen@.mimosa.com> wrote in message
news:Ogsx6I2YEHA.3012@.tk2msftngp13.phx.gbl...
> It will go ahead and configure IIS to use asp.net 2.0 for your existing
> asp.net sites resulting in the fact that you can no longer debug your
> asp.net v1.1.4... applications with visual studio.net 2003.
> I have spent some time wondering why i could no longer debug my
> existing apps. right after my instalation completed and at my big
surprise,
> IIS has "configured" them to use
> asp.net 2.
> When i manually corrected this, things started working again.
> I wondwer how many other untold stories there are out there about this
> issue.
>
> Thanks
>
> JB
You can get a free tool to switch versions on demand from
http://www.denisbauer.com/
--
<%= Clinton Gallagher
A/E/C Consulting, Web Design, e-Commerce Software Development
Wauwatosa, Milwaukee County, Wisconsin USA
NET csgallagher@. REMOVETHISTEXT metromilwaukee.com
URL http://www.metromilwaukee.com/clintongallagher/
"bredal Jensen" <bred.jen@.mimosa.com> wrote in message
news:Ogsx6I2YEHA.3012@.tk2msftngp13.phx.gbl...
> It will go ahead and configure IIS to use asp.net 2.0 for your existing
> asp.net sites resulting in the fact that you can no longer debug your
> asp.net v1.1.4... applications with visual studio.net 2003.
> I have spent some time wondering why i could no longer debug my
> existing apps. right after my instalation completed and at my big surprise,
> IIS has "configured" them to use
> asp.net 2.
> When i manually corrected this, things started working again.
> I wondwer how many other untold stories there are out there about this
> issue.
>
> Thanks
>
> JB
The problem here is that the new tool ships with its own "embeded" web
server so i do not
understand why it has to mess with IIS ?
"clintonG" <csgallagher@.REMOVETHISTEXT@.metromilwaukee.com> wrote in message
news:ulwexL4YEHA.3988@.tk2msftngp13.phx.gbl...
> You can get a free tool to switch versions on demand from
> http://www.denisbauer.com/
>
> --
> <%= Clinton Gallagher
> A/E/C Consulting, Web Design, e-Commerce Software Development
> Wauwatosa, Milwaukee County, Wisconsin USA
> NET csgallagher@. REMOVETHISTEXT metromilwaukee.com
> URL http://www.metromilwaukee.com/clintongallagher/
>
> "bredal Jensen" <bred.jen@.mimosa.com> wrote in message
> news:Ogsx6I2YEHA.3012@.tk2msftngp13.phx.gbl...
> > It will go ahead and configure IIS to use asp.net 2.0 for your existing
> > asp.net sites resulting in the fact that you can no longer debug your
> > asp.net v1.1.4... applications with visual studio.net 2003.
> > I have spent some time wondering why i could no longer debug my
> > existing apps. right after my instalation completed and at my big
surprise,
> > IIS has "configured" them to use
> > asp.net 2.
> > When i manually corrected this, things started working again.
> > I wondwer how many other untold stories there are out there about this
> > issue.
> > Thanks
> > JB
0 comments:
Post a Comment