Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Trust an Assembly

0 views
Skip to first unread message

Robert

unread,
Jan 5, 2004, 2:45:16 PM1/5/04
to
I have created a WinForm application that calls a Web
Service. Everything works fine on my development machine
but once I deploy it onto a user's machine, I get
security issues. I have to go to the user's machine and
run a Framework 1.1 wizard (Trust an Assembly), browse to
my Web Service and set the trust to full trust to get the
application to work. Is there a way to handle this
security or trust issue in the setup package so that I do
not have to touch the user's machine except to install
the application?

Thanks,

Robert

Chris Botha

unread,
Jan 5, 2004, 6:00:57 PM1/5/04
to
This does not sound right. Is your app physically installed/copied onto the
client machine? I've done this many times (Win 2000 and 98) without any
problems. If the app or an assembly (a DLL) that the app uses is on a
network drive, then you will have security issues.

"Robert" <rh...@wfubmc.edu> wrote in message
news:079801c3d3c4$7110e810$a001...@phx.gbl...

Robert

unread,
Jan 7, 2004, 12:34:40 PM1/7/04
to
Sorry, in my haste to get this out, I was not accurate.
The issue has to do with trusting an assembly (EXE) that
physically resides on a network drive but is being
accessed and run locally on a user's machine. You are
correct, the Web Service is not an issue. When setting
the icon up on each user's machine, I have to run the
Framework 1.1 Wizard that allows me to browse to the
Assembly (EXE) on the network and set the trust to full
trust. I want to be able to accomplish this in a setup
program. Is this possible?

Thanks,

Robert

>.
>

Chris Botha

unread,
Jan 7, 2004, 1:51:11 PM1/7/04
to
You know what, as you can see, this web services newsgroup is pretty dead,
and I think regarding your requirement on this security issue you may get a
lot more action on the "dotnet.framework" and "dotnet.windowsforms"
newsgroups. The fact that the app is using a web service is irrelevant in
this case, so don't even mention it.
Another option is no-touch deployment, but you may also run into security
issues if the app has to write to the local disk, etc.


"Robert" <rh...@wfubmc.edu> wrote in message

news:028501c3d544$87551b60$a101...@phx.gbl...

0 new messages