I'm developing a solution for a client using the ClickOnce technology. This client has a fair amount of legacy functionality in ASP.NET 1.1. During the transition period, my thought was to build a ClickOnce application that featured new functionality in the ClickOnce WinForms application. To support the legacy ASP.NET functionality within the one application, my thought was to embed a WebBrowser control within the application that would route the user to the existing ASP.NET web site. However, when I do this, the ClickOnce Security Settings require full trust.
My question is two-fold. One: Is there another/better way I could achieve a similar result Two: If we're stuck with the full trust ClickOnce Security Setting, what is the real danger
I greatly appreciate any feedback you can provide.
Thanks
Jeff
Using a WebBrowser Control in a ClickOnce Application
Hot Topic
- unmanaged dll, struct runtime issues
- New to Threading Help please
- Cross Threaded data access...
- Threads, Events & BeginInvoke
- Insert data with back date (current date-1) in SQL Server
- What .Net Framework to use???
- Visual Studio .NET & importing an existing site
- How to force use of .NET 1.1
- Update requires a valid UpdateCommand when passed DataRow collection with modified rows.
- Firewall\NAT friendly remoting
.NET Development
- Request for the permission of type FileIOPermission failed
- Click Event for Member of Label Array
- Will AnyCPU cause binaries to run as 64-bit on x64 machine
- Exclude schema when sending typed dataset through web services
- Configuration system failed to initialize, when try to consume a webservice on GINA
- Cannot unload assemblies that you create and load by using script in XSLT
- VB. NET decompiler
- TCP Connections and Web Service Calls (Reposted from WebServices newsgroup)
- System.Reflection (Reading Assemblies)
- Unwanted changes to Titlebar text...
Using a WebBrowser Control in a ClickOnce Application
hunny
If you grant the application FullTrust that means it has the same level of access to the machine that any native application does. For instance, it can call native code, run unverifiable code, etc.
If you've written the application yourself, and know that it's trustworthy, then you might consider this an accceptable approach. However, if you're running a third party application from an Internet site, you almost certainly don't want to grant them FullTrust
-Shawn