Thanks for your reply. I realize that it will halt any use of the live
version, however I was getting errors that were only occuring in Production
and I wanted to be able to catch them. However I subsequently found that
some of my errors are/were due to the way ASP.Net / IIS is configured, for
some reson I the Admin user has to log into the server and attempt to do some
data input in the form. Otherwise, there are login errors for everyone,
(table(0) does not exist) this is the table that contains a users auth info
as well as the forms they see. Then after I login to the server as the admin
user, unless I use the web application we don't see the linked Tif files as
if the path is not valid. If I then open a web form that contains any one of
these tif's at the server console once cures for all the remote users.
TIA
JeffP....
[quoted text, click to view] "m.posseth" wrote:
> first of all it is alway bad parctice to develop on a live production server
>
> the debug components are a seperate install on the visual studio DVD ,
> Insert the DVD in the server when the Visual studio installation menu
> appears look to the text in the bottom , you will see there a text saying
> something like "Install server components" install these components and you
> can debug on the server ..
>
> However as i said above this is bad practice as debugging should be
> performed on your dev / staging server , when debugging the project the hole
> worker process is halted and might interfere with extrenall users ( so
> customers might encounter a non responsive website , or a website that loses
> state info every time you hit the start / stop / pause / debuging buttons )
>
>
> you have been warned ! :-)
>
>
> regards
>
> Michel Posseth [MCP]
>
>
>
> "JeffP->" <JeffP@discussions.microsoft.com> wrote in message
> news:EA4E02B1-6F98-4251-B72A-148D65C0A757@microsoft.com...
> > Win2K Server .Net 1.1x framework, devenv.exe is not installed.
> > I copied my entire project to a web folder.Dev on the production server
> > and
> > added the production webconfig
> >
> > When I tried to start debug the web app from my local machine, I got the
> > msg
> > that something isn't setup correctly to debug on the server.
> >
> > Link or steps to cure?
> >
> > TIA
> >
> > JeffP...
>
>
first of all it is alway bad parctice to develop on a live production server
the debug components are a seperate install on the visual studio DVD ,
Insert the DVD in the server when the Visual studio installation menu
appears look to the text in the bottom , you will see there a text saying
something like "Install server components" install these components and you
can debug on the server ..
However as i said above this is bad practice as debugging should be
performed on your dev / staging server , when debugging the project the hole
worker process is halted and might interfere with extrenall users ( so
customers might encounter a non responsive website , or a website that loses
state info every time you hit the start / stop / pause / debuging buttons )
you have been warned ! :-)
regards
Michel Posseth [MCP]
[quoted text, click to view] "JeffP->" <JeffP@discussions.microsoft.com> wrote in message
news:EA4E02B1-6F98-4251-B72A-148D65C0A757@microsoft.com...
> Win2K Server .Net 1.1x framework, devenv.exe is not installed.
> I copied my entire project to a web folder.Dev on the production server
> and
> added the production webconfig
>
> When I tried to start debug the web app from my local machine, I got the
> msg
> that something isn't setup correctly to debug on the server.
>
> Link or steps to cure?
>
> TIA
>
> JeffP...
