Do I really need to delete the Live Services project just to change the logo?

Question

I recently modified the logo in my Mesh project and then ran it and noticed that Live mesh wasn't taking the new logo into account. I'm fine with having to destroy the Mesh project during the CTP every time I need to change the logo.. but during production, if I need to modify my logo, I'm not going to want to _lose everyone's data_ that was using my Mesh app just so that I can change the logo.

In the future, can we make logos something that is re-evaluated during the post-build update sequence?

---

The .NET Addict - http://dotnetaddict.dotnetdevelopersjournal.com

Answer 1

When you mention Mehs project, are you working with mesh-enabled web applications? I ask because I wanted to make sure where this logo shows up.

---

Program Manager - Live Services / Live Framework

Answer 2

Hi, Kevin,

We tested it here again that when we upload a new package with new logo, both exist instance and new instance have new logo. You shouldn't have to destroy the package and create a new one with new logo. I'm wondering whether the new package is uploaded successfully. Can you use Fiddler to check if the new logo is uploaded and downloaded?

Thanks

Rong Cao MSFT

Answer 3

Ken,

If you're uploading using the VS tools, make sure the app instance you're looking at is the debug version that VS uploaded.  An app that is configured as a single-instance app should just work (only one version can be exposed, so it will be the debug version), but if you're working on a multi-instance Mesh-enabled web app, you could have a debug app instance managed by VS and one or more non-debug app instances that will not track with changes uploaded by VS.  Launching the app from VS should always show you the logo / resources defined in your current VS project.

If an app instance is created before VS has uploaded the app to the cloud, that app instance will be bound to the original version of the app resources and won't track with updates to the debug version uploaded by VS.  (Sequence:  manually upload zip file created by VS tools, then install and create app instance on Live Desktop in the browser, then give VS the app self link for the project.  If the app is multi-instance, VS will create a new app resource feed and app instance with a "- Debug" suffix in the instance name.

-Danny

---

http://dannythorpe.com

Answer 4

When I uploaded the new mesh application (Mesh-enabled web application, all Silverlight) by hitting F5 in Visual Studio, the new logo did not appear to take effect. Later, when I looked at my resources through the Resource model browser, I noticed that there were two copies of my application in the mesh but only one showed up on my desktop.

Could that be related or is this just a fluke?

---

The .NET Addict - http://dotnetaddict.dotnetdevelopersjournal.com

Answer 5

There is a known issue with propogation of mesh apps from the cloud to the local desktop when the app has multiple resource feed versions.  This is the case with a mesh app uploaded to the cloud by VS.

Workarounds are:

1. Run your app in Live Desktop in the browser
2. Or, remove the app self link from the meshproj properties in VS to prevent VS from uploading to the cloud and upload the VS generated zip file manually.

-Danny

---

http://dannythorpe.com

Answer 6

Actually, the problem was with the Live Desktop website. I just reproduced this problem again:

1. Delete Logo.png
2. Paste in Logo_new.png
3. Rename Logo_new.png to Logo.png
4. Clean
5. Rebuild
6. Hit F5
7. Icon that shows up in Live Desktop is the old one, not the new one (I put a big red X in my new icon just to be sure)

This brings up another issue - no matter what icon I use for my app, the icon on my desktop is the Live Mesh "cube" icon, not my app icon.

My app is a multi-instance app. Again, I would rather not have to delete the app every time my designer-in-arms adds a new gradient to our logo :)

---

The .NET Addict - http://dotnetaddict.dotnetdevelopersjournal.com

Answer 7

Ah, I think I see the problem.  (Or at least *a* problem, I don't know if it's the cause of your issue. ;>  )

The logo.png uploaded through the dev portal gets a content-type of image/png in the application resource feed. 

The logo.png uploaded by VS gets a content-type of application/octet-stream, which I'm pretty sure isn't going to display in any browser image element.

Stepping through our VS code, it looks like we're setting the content-type correctly (image/png) on the request, but it's definitely not image/png at the other end of the pipe.  I'll have to dig into this a bit more to see if the content-type is getting mangled on its way up to the cloud or in the cloud itself.

-Danny

---

http://dannythorpe.com

Answer 8

Hi, Kevin,

I think Danny already figured out ways to fix the problem. You should expect an updated package soon. Thank you for going extra miles to narrow down the problems. We really appreciate it.

Thanks

Rong Cao MSFT

Answer 9

Kevin,

The wrong content-type on the logo.png file in the debug resource feed is definitely a bug that needs to be fixed, but fixing it does not change the icon update issue you reported. 

For the moment, the only way to get a new logo to appear in the app shortcut on the Live Desktop is to construct a new project on the dev portal and upload your app to the new project.

-Danny

---

http://dannythorpe.com

Answer 10

Right - this is the problem I was pointing out. Hopefully this will be fixed for the next release because I don't want to lose all of my mesh data just to upload some new design assets.

---

The .NET Addict - http://dotnetaddict.dotnetdevelopersjournal.com

Answer 11

This issue has been fixed with Jan 2009 CTP of Live Framework Tools.
http://blogs.msdn.com/liveframework/archive/2009/02/02/live-framework-tools-january-ctp.aspx

---

This posting is provided "AS IS" with no warranties, and confers no rights.