Sometimes ago, when I added a webreference, visual studio created a
Reference.vb proxy class. In vs.net 2005, I don't see it. instead it
adds .disco, .discomap, .wsdl. when I try to run the web app, it
attemps to write to the c:\windows\temp directory.
I hate that approach. because I DO not want to give IIS the
permissions to write to windows temp directory due to potential
security problems. there might be other process writing to that dir
that I do not want the web app to access.
Is there a way to instruct visual studio to create the proxy class in
the design and all I have to do is to upload the class to the web app
like we did it before?
Is there a way to tell asp.net where to create the proxy class. c:
\windows\temp is not the directory I wish IIS to access really!
thanks for all replies.
Reference.vb proxy class. In vs.net 2005, I don't see it. instead it
adds .disco, .discomap, .wsdl. when I try to run the web app, it
attemps to write to the c:\windows\temp directory.
I hate that approach. because I DO not want to give IIS the
permissions to write to windows temp directory due to potential
security problems. there might be other process writing to that dir
that I do not want the web app to access.
Is there a way to instruct visual studio to create the proxy class in
the design and all I have to do is to upload the class to the web app
like we did it before?
Is there a way to tell asp.net where to create the proxy class. c:
\windows\temp is not the directory I wish IIS to access really!
thanks for all replies.
Comment