The issue with creating publish.htm for browser-hosted WPF via Publish Wizard is a known bug and a future release will carry a fix.
Meanwhile you can either type the Url in your browser's location bar (as someone suggested) or employ a test HTML page with a hyperlink to your .xbap. Yes, you do need to configure MIME types on your web server though. This article has details.
I guess I need more information. You are using the VS 2005 tool to publish a click once application, but you unchecked the 'Automatically generate deployment web page' option. When you publish is should compile and kick out your application (.exe and .dlls) along with any files you specifically added. It also creates several other files:
.application, .manifest, setup.exe
I don't know of any .xbap exention file. When you install the .NET 2.0 Framework it registers '.application' as a file type assocaited with the 'Application Manifest' tool, so when it downloads the .application file it automatically launches the Click Once tool. If you change the extensions or attempt to run anything other than the '.application' file it won't work. The .application file references the .manifest file.
That will launch the app for testing purposes. Or you can create a test page by hand...it wouldn't be very hard. Just add references to the above URLs in a standard HTML page.
I unchecked "Automatically generate deployment webpage" now...
mkbbrt
The issue with creating publish.htm for browser-hosted WPF via Publish Wizard is a known bug and a future release will carry a fix.
Meanwhile you can either type the Url in your browser's location bar (as someone suggested) or employ a test HTML page with a hyperlink to your .xbap. Yes, you do need to configure MIME types on your web server though. This article has details.
You can post WPF-related queries such as this in the Windows Presentation Foundation (Avalon) forum.
chowdharyrohit
That definitely complicates things...and I have no idea what problems that introduces (haven't started playing with Avalon yet).
Good Luck.
Bigs
No problem, thx for trying. Regular WinFX apps run fine. It's probably just too soon to be testing the Navigation ones...
Regards.
slimjen1
I'm trying to publish WinFX (avalon) web browser apps using the Jan bits.
Frederik Carlier
I guess I need more information. You are using the VS 2005 tool to publish a click once application, but you unchecked the 'Automatically generate deployment web page' option. When you publish is should compile and kick out your application (.exe and .dlls) along with any files you specifically added. It also creates several other files:
.application, .manifest, setup.exe
I don't know of any .xbap exention file. When you install the .NET 2.0 Framework it registers '.application' as a file type assocaited with the 'Application Manifest' tool, so when it downloads the .application file it automatically launches the Click Once tool. If you change the extensions or attempt to run anything other than the '.application' file it won't work. The .application file references the .manifest file.
cpvgd
You don't really need a test page...just open a browser and type the URL in directly. For instance:
http://localhost/MyApp/MyApp.application
or
http://localhost/MyApp/setup.exe
That will launch the app for testing purposes. Or you can create a test page by hand...it wouldn't be very hard. Just add references to the above URLs in a standard HTML page.
clintonG
Karl Costenbader
I already tried that launching something like:
http://www.foobar.com/WebBrowserApplication1.xbap
I'm trying to launch a navigation app with the .xbap extension.