Why is XamlT clickonce deployed?

Thu, 07 Jun 2007 12:20:35 GMT

Anybody else like to see an .exe version of XamlT in addition to click once? Personally, I find it annoying that I need to put Reflector someplace myself...I love Petzold's XamlCruncher because it is easy to install.

Internal mail thread, read from bottom:

From: MS Guy
Wouldn't be the first time I was an oddball... :)

----

From: Rob Relyea
How typical are users like u?

I've never heard push back against clickonce before.

----

From: MS Guy

Win+R. :)

I've got a Utilities directory that I mirror across my machines. Anything that's in there is automatically available everywhere. Like Reflector. :)

I guess I just dislike installers in general since they require elevation, can break stuff, I can't see what they're doing, etc..

----

From: Rob Relyea
I do that so I can update the app automatically.

Do you not want a start menu entry?

How do you like launching your apps?

----

From: MS Guy  
Subject: Why is XamlT clickonce?

I'm the kind of guy that doesn't like installing stuff I don't need to. :) Are there limitations to making it a standalone EXE?

XamlT - a new xaml-centric class browser & xaml utility

Tue, 05 Jun 2007 18:04:17 GMT

Check out http://xamlT.com.

I've published a new tool called XamlT which may help Silverlight 1.0, Silverlight 1.1, Workflow Foundation (WF) and WPF users who are trying to understand the Xaml Vocabularies that are available. Beyond that, the tool has a little Xaml -> C# engine that I've been working on.

I have a few credits in Tools/About... (which I plan to add to)

Try it out...

Rob Relyea: XamlT

Why is XamlT clickonce deployed?

XamlT - a new xaml-centric class browser & xaml utility