Subject: new fat purging method

From: Doc Oz Show Exclusive <[email-masked]>
Date: Thu, 14 Aug 2014 08:07:47 -0700

Just In: Weight-Loss Trick for EVERY Body Type

Melt Fat no matter what your shape. 
This proven tip will have you shedding pounds in a few days.

Kiss that Fat goodbye immediately.

View DocOz Clip: http://www.begbugafter.com/women-2346/oprah-tip.html
Episode 401

Get comfortable in you own skin once and for all...

- DocOz Show

To stop further notifications - visit http://www.begbugafter.com/g5.r
or write to Daily Updated Alerts
9306 BOVA CT
Louisville, KY 40291
-
-
-
\
fyi...this did not work for me. My settings have always been: [assembly: AssemblyVersion("1.0.0.0")] [assembly: AssemblyFileVersion("1.0.0.0")]   tbone Feb 16 '11 at 16:31
  	 	
it's too bad too see MS did not fixed this yet! Such an annoying bug. Thanks for the fix. Has anyone reported this at MS side? Could we have a link on the follow-up? I believe it was supposed to be addressed in SP1, but I don't have the guts to install it yet. Maybe someone can report back if they have installed it already. If you currently have [assembly: AssemblyVersion("1.0.0.0")], replace it with [assembly: AssemblyVersion("2.0.0.0")] (i.e. '2' instead of the '1'). It worked for me. Although I haven't checked, it's possible that simply changing the version to anything other than what you've got now can fix this problem. Works for dll too! VS says cannot copy the dll and after changing BOTH [assembly: AssemblyVersion] and [assembly: AssemblyFileVersion()] from 1.0.* to 2.0.0.0, it worked.Wish I could give you +10 I had this same problem. I had three projects under one solution, an asp.net website project, a vb.net library project and C#.net library project. Website project build s
 uccessfully but other project did not build and gave the same exception as above. I tried changing the AssemblyVersion but it did not work. What i tried was changing the readonly property. Removed readonly property and it worked. Now all the three projects in the solution build successfully. Now i again see the readonly property of the two project folder and i see they are readonly still, but it works. Even better: this isn't just the auto-increment. I can't change AssemblyVersion, whether with my own program, Notepad++, or even VS itself. On the other hand, it seems that only changes to AssemblyVersion trigger it. AssemblyFileVersion and AssemblyInformationalVersion can be freely changed.