Life in my own company

Its all up to me.
posts - 137, comments - 166, trackbacks - 113

My Links

News



Twitter



Tag Cloud

Archives

Post Categories

Play

Work

Is ClickOnce broken?

Technorati Tags: ,,,

We've been struggling with ClickOnce using mage.exe and MageUI.exe to manually deploy the application.  Since we're doing continuous integration, we need this to work.

I've spent 4 hours with MS support trying different combinations of deployment to no avail.  We've tried everything.  Today, I built a sample application to see if it was our projects or MS.  Using Visual Studio 2008, I created a new WPF application and left everything at it's default.  The XAML for the Window1 file is:

<Window x:Class="ClickOnceTrial.Window1"
    xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
    xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
    Title="Window1" Height="300" Width="300">
    <Grid>
        <TextBlock Text="Hello World"/>
    </Grid>
</Window>

Then, change the target for the project to be .net 3.0 instead of .net 3.5.  Build and use MageUI to create the application manifest (using just the single exe that's created) and the application file itself.  Then try your install.  With us, it fails.  You don't get much simpler than the above application either.

MS says this is the first report they've had.  Are we alone in we're doing?  Has anyone else successfully been able to do what's been described above?  Is it just something that's broken with our web server setup (server 2003, IIS6, .net 3.5)? 

I'd love to hear any stories about what's working and what's not.

Update:  Changed it to targeting 3.5 and it didn't make a difference.

Update2:  We found the problem and have a work around!  Yeah!  See this post for details.

Print | posted on Tuesday, December 04, 2007 1:34 PM |

Feedback

Gravatar

# re: Is ClickOnce broken?

I got clickonce rocking with teambuild and WPF. It's all with vs 2005 though.
12/4/2007 3:00 PM | Tim Hibbard
Gravatar

# re: Is ClickOnce broken?

We were killing it with 2005 as well, but as soon as we started building with msbuild 3.5 and mage 3.5, things fell apart. :(
12/4/2007 3:17 PM | Robert
Gravatar

# re: Is ClickOnce broken?

Good to know. I was planning on migrating this weekend. I use the MSBuild Community Tasks, maybe that could point you in the right direction. I wrote a simple guide here:
http://geekswithblogs.net/thibbard/archive/2007/06/01/Publishing-a-ClickOnce-app-with-TeamBuild.aspx
12/4/2007 3:23 PM | Tim Hibbard
Gravatar

# re: Is ClickOnce broken?

We're not using MSBuild to do a publish in the project files, but using Mage instead. Maybe I should try that.
12/4/2007 3:27 PM | Robert
Gravatar

# re: Is ClickOnce broken?

Cool...please post your findings!!
12/4/2007 3:30 PM | Tim Hibbard
Gravatar

# re: Is ClickOnce broken?

I just ran into this yesterday oddly enough. Our build environment is setup like this:

VS 2008
TFS 2005
Mage for .Net 2.0 (Upgraded to 3.5 though same errors)

I cannot for the life of me get anything to deploy with Mage and manifests I build myself. However if I publish a .Net 3.5 app through VS2008 then ClickOnce works. Oh and the fun part, your site is the most documentation I've found on this issue.
12/5/2007 11:38 AM | Chris

Post Comment

Title  
Name  
Email
Url
Comment   
Please add 3 and 5 and type the answer here:

Powered by: