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.
Mr. Arnold - 03 May 2008 12:55 GMT
> 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
[quoted text clipped - 12 lines]
> 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!
Why don't you just use the .Net WDSL utility at the .Net Command Prompt to
generate the proxy class to include in your project? That way, you don't
need a .disco or anything else or writing to some temp directory.
mr t - 05 May 2008 22:19 GMT
> Why don't you just use the .Net WDSL utility at the .Net Command Prompt to
> generate the proxy class to include in your project? That way, you don't
> need a .disco or anything else or writing to some temp directory.- Hide quoted text -
>
> - Show quoted text -
yes, how do I access the .net command prompt?
Mr. Arnold - 07 May 2008 01:02 GMT
> Why don't you just use the .Net WDSL utility at the .Net Command Prompt to
> generate the proxy class to include in your project? That way, you don't
> need a .disco or anything else or writing to some temp directory.- Hide
> quoted text -
>
> - Show quoted text -
yes, how do I access the .net command prompt?
-------------------
It's one of the tools in VS 2003, 2005, 2008 -- the .Net Command Prompt.
The .Net wdsl.exe tool is part of the .Net Framework. So, maybe you can find
out how to execute the WDSL.exe utility without the .Net Command Prompt of
VS.
You should use Google and find out how to use the WDSL.exe
Maybe, there is some free WDSL utility for .Net too.