I would like to customize the user install process for my Silverlight application. I would need to repeatedly go through the installation process on my development workstation Short of uninstalling before each change I make and going through the install process again, is there a way to make my browser think Silverlight is not installed?
Yes, there is a way to make your browser think SL is not installed.
In Internet Explorer 8, I can go to Tools > Manage Add-ons. From there, I select to Show "All add-ons." I then click on Microsoft Silverlight and click "Disable."
I saw Tim Heuer do this process to demonstrate the look of Silverlight being uninstalled in an application.
I imagine there's a way to disable plug-ins, add-ons, extensions, etc. for other browsers.
You could set up a Virtual PC or Virtual Box instance and keep resetting it to a "before Silverlight was installed" snapshot.
Related
Is this dll not compatible with windows store app, Or is there any other way to achieve the same.
I tried adding it from nuget package also but not happening, I am getting this error:
"Severity Code Description Project File Line Suppression State
Error Package restore failed. Rolling back package changes for 'Solution'."
As far as I'm concerned, you need to intall the Windows Identity Foundation as well as the WIF SDK and then restart the application for the effect to work.
For Windows 10 device, Windows Identity foundation is not an istall but a Windows feature need to be enabled.
Enter Control Panel from Start menu
Click program and features
Choose turn Windows feature on or off
Choose Winodws Identity Framework, click OK
Restart your machine
A similar question here that could be helpful to you. As Moory said in the comment, he fixed this issue by adding the reference below to the csproj file:: ( .
Please also try it. Thank you.
I have my application wrote in WPF. Now, i want it to run in browser so I've read about it and I know that XBAP is my solution.
What is my problem? It won't run on my PC. I checked every popular browser (chrome, FF, IE, opera) and nothing. Browsers can't handle .xbap files and just downloads it.
I try and try and nothing but above happened. Can anyone guess why it don't work? Is it deprecated technology, i have too-new browsers or what? Every entries I found about it are 2-4 years old.
Firstly for Internet Explorer (IE9 onwards) you need to ensure that you have enabled XBAP/XAML support:
For Firefox and Chrome you have to do something a bit different:
How can I get my XBAP to run in my browser instead of downloading it on Windows 7?
But in addition to the above you need to be aware that when you run an XBAP application it runs in the Internet Zone....so your biggest problem is that normally you don't have full-trust...therefore your application can't call privileged code...if it tries to then you get security exceptions.
http://www.tarkia.com/blog/tag/difference-between-wpf-application-and-xbap-application/
http://www.tarkia.com/blog/2009/11/26/understanding-xbap-full-trust-partial-trust-certificates-and-more%E2%80%A6/
One way to get your XBAP to be "trusted" is to get it signed with a certificate (you should purchase a proper one from Verisign rather than use a test certificate) and deployed with ClickOnce.
http://blogs.microsoft.co.il/blogs/maxim/archive/2008/03/05/wpf-xbap-as-full-trust-application.aspx
http://blogs.microsoft.co.il/blogs/maxim/archive/2008/03/31/how-to-run-wpf-xbap-application-in-full-trust-mode-post-2-certificate-extraction.aspx
http://scorbs.com/2007/01/10/xbap-trust-levels/
Or you can keep your application as a regular WPF .EXE and use ClickOnce to deploy it from a website but run it locally with full trust.
not straight forward way, you can find you answer Microsoft MSDN Forum
I made a setup project for my windows forms application and then installed it. It properly created a shortcut on desktop. Now when I double click it to open, it shows a progress bar like thing saying Configuring application. After that, my windows form appears and runs normally.
I have no clue why this is happening. My earlier version for the same application was running properly with o. Also if I install the previous version, it starts normally without any problems. Only the setup files that I am creating now are showing this problem.
Any one having any clue...
You created a ClickOnce installation. You probably wanted to create a standard Setup Project. IIRC, there was some issue with this type of project in Visual Studio 2010, as in the project type is being depreciated, but I can't seem to find anything about that now.
Other alternatives are using WiX or the limited edition of InstallShield.
Oddly enough, the ClickOnce installer is pretty good, assuming you have the infrastructure to support it (a spot on the web where you place updates) and don't mind the nonstandard behavior (that weird dialog on start). Frankly, installer technologies right now in the .NET world suck. They're all extremely complicated and fail to insulate the developer from the intricacies of how installers work with Windows.
To turn off ClickOnce, IIRC, do the following:
Uncheck "Sign the ClickOnce manifests" on the Signing tab
Uncheck "Enable ClickOnce security settings" from the security tab
remove any references to "System.Deployment" from your projects
I have a couple questions regarding Silverlight 4:
Does running a Silverlight 4 app, out of browser, in full trust, require the
user to respond to a dialog asking for permission? If so, is there a way around this?
If the answer to #1 is yes, is the user prompted with the same dialog each time
the app is updated?
Is full trust only available in an out of browser app, or is it available via the browser as well?
If an app is installed out of browser, does the user have to actually do
anything to get the app installed? Or is it all transparent?
Are there any other installation issues with Silverlight 4 apps that would
make installation problematic for a user.
The main reason I ask all this is because we're considering Silverlight 4 for our corporate internal apps and we'd like the deployment process to be seamless and transparent. And since they are internal apps, we don't need our users to confirm it's ok to install in full trust.
No way around this, the user will be asked whether they trust the application the dialog includes a warning that the application requires elevated trust.
No the application can update itself without their seeing this same elevated trust warning again.
Currently in SL4 its only available to OOB apps. SL5 will allow administrators to extend elevated trust to in browser apps via group policy.
The inbrowser version needs to give the user a some form of UI (button) to invoke installation (the ability to install is also added to the default context menu for the application). The user will then need to agree to the dialog presented. After that the user will need to close their current usage and manually start the newly installed app.
Not that I know of, a part from the presence of Silverlight runtime there are no other dependencies.
For you requirements you might be better looking at a different technology right now but SL5 may fit your needs in the future.
It's possible to install a Silverlight application as an OOB application with elevated permissions using the command prompt. If you have a system adminstrator controlling what the users get installed on their computers you can install the application without bothering the user.
When the application is installed an update will not prompt the security dialog. But in some scenarios it makes sense to restart the application.
In SL4 elevated trust requires the application to run OOB.
Have a look at this article about signing Silverlight applications it might help you with several of these issues. By signing you could overcome trust issues and the users to be bothered with dialogs.
EDIT Read this too it explains more about trusting the publisher and updating
I'm developing a Windows Form application that will typically minimize to the system tray. Being new to .net, what would the easiest approach be for packaging/deplopyment that allows:
The application ensure it puts itself into the startup menu, or something equivalent to this.
Easy updates—like those apps that periodically check for updates. When there is an update to install, it should automatically download it via the internet and install it.
I read that using the ClickOnce/standard deployment approach that ClickOnce won't work because it doesn't support the ability to put the application in the START-UP Menu during installation. Is that true? If so, what should I use?
Thanks.
ClickOnce apps can (and automatically are) placed in the start menu. You can optionally have a shortcut placed to them on the desktop as well.
ClickOnce apps cannot be installed in the "system start up" folder; that is, cause them to start when Windows starts. Don't confuse the "start up" folder with the Start Menu.
If you're just starting out with .NET, I'd recommend ClickOnce. It saves lots of installation headaches and automates everything from updates, to start menu shortcuts, to desktop shortcuts, to file associations. It's a decent technology. The deployment couldn't be simpler. In Visual Studio, just click Build->Deploy, specify where you want to deploy to (FTP, network share, etc.) and you're all set.
An ordinary Windows Installer project would do the trick. All the user needs to know how to do is click Run...Next...Next...Next...Finish.
Choosing Between ClickOnce and Windows Installer
http://msdn.microsoft.com/en-us/library/ms973805.aspx
Windows Installer provides the Start Menu support and easy updating features that you require. It also has the ability to check for updates.
I am less familiar with ClickOnce, but it does have some of the same features. An overview of the feature differences between Windows Installer and ClickOnce is here:
http://msdn.microsoft.com/en-us/library/142dbbz4.aspx
In particular, there are differences in the level of permissions granted to the installer, as well as driver installation and menu shortcut capabilities.