<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/atom.xsl" media="screen"?><feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en"><title type="html">Jamshed's blog</title><subtitle type="html">&lt;br&gt;&lt;br&gt;

</subtitle><id>http://blogs.msdn.com/jamshedd/atom.xml</id><link rel="alternate" type="text/html" href="http://blogs.msdn.com/jamshedd/default.aspx" /><link rel="self" type="application/atom+xml" href="http://blogs.msdn.com/jamshedd/atom.xml" /><generator uri="http://communityserver.org" version="2.1.61025.2">Community Server</generator><updated>2006-06-26T21:29:00Z</updated><entry><title>File rollback to last Service Pack when uninstalling an update for the Microsoft .NET Framework 1.0, the Microsoft .NET Framework 1.1, Visual Studio .NET 2002 or Visual Studio .NET 2003</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/jamshedd/archive/2007/07/11/file-rollback-to-last-service-pack-when-uninstalling-a-net-framework-1-0-or-1-1-update.aspx" /><id>http://blogs.msdn.com/jamshedd/archive/2007/07/11/file-rollback-to-last-service-pack-when-uninstalling-a-net-framework-1-0-or-1-1-update.aspx</id><published>2007-07-12T05:11:00Z</published><updated>2007-07-12T05:11:00Z</updated><content type="html">Yesterday was patch Tuesday, and Microsoft released security updates targeting a few products including the .NET Framework (see security bulletin MS07-040 ). This bulletin contains updates for the .NET Framework 1.0, 1.1, and 2.0. The updates for the .NET Framework 1.0 and .NET Framework 1.1 are noteworthy because of a drawback both updates suffer from. Lets say you have an update for the .NET Framework installed and you then install a second update. Later on if you uninstall the second update, you...(&lt;a href="http://blogs.msdn.com/jamshedd/archive/2007/07/11/file-rollback-to-last-service-pack-when-uninstalling-a-net-framework-1-0-or-1-1-update.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=3823400" width="1" height="1"&gt;</content><author><name>jamshedd</name><uri>http://blogs.msdn.com/members/jamshedd.aspx</uri></author><category term="Security Updates" scheme="http://blogs.msdn.com/jamshedd/archive/tags/Security+Updates/default.aspx" /><category term="Security" scheme="http://blogs.msdn.com/jamshedd/archive/tags/Security/default.aspx" /><category term="Update" scheme="http://blogs.msdn.com/jamshedd/archive/tags/Update/default.aspx" /><category term=".NET Framework" scheme="http://blogs.msdn.com/jamshedd/archive/tags/.NET+Framework/default.aspx" /><category term="Visual Studio" scheme="http://blogs.msdn.com/jamshedd/archive/tags/Visual+Studio/default.aspx" /></entry><entry><title>Registry Key based detection for .NET Framework and Visual Studio updates</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/jamshedd/archive/2007/06/16/registry-key-based-detection-for-net-framework-and-visual-studio-updates.aspx" /><id>http://blogs.msdn.com/jamshedd/archive/2007/06/16/registry-key-based-detection-for-net-framework-and-visual-studio-updates.aspx</id><published>2007-06-16T21:01:00Z</published><updated>2007-06-16T21:01:00Z</updated><content type="html">There is often a need to have a way to detect whether or not a certain update for the .NET Framework or Visual Studio is installed on a PC. A user might easily go and look this up in ARP (Add-Remove Programs), but if you are an IT administrator for an enterprise you do not want to walk around and look this up one machine at a time for a few hundred or even a few thousand machines. What you need in that case is a scriptable/deployable way of detecting whether the update is question is installed. One...(&lt;a href="http://blogs.msdn.com/jamshedd/archive/2007/06/16/registry-key-based-detection-for-net-framework-and-visual-studio-updates.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=3344264" width="1" height="1"&gt;</content><author><name>jamshedd</name><uri>http://blogs.msdn.com/members/jamshedd.aspx</uri></author><category term="Update" scheme="http://blogs.msdn.com/jamshedd/archive/tags/Update/default.aspx" /><category term=".NET Framework" scheme="http://blogs.msdn.com/jamshedd/archive/tags/.NET+Framework/default.aspx" /><category term="Visual Studio" scheme="http://blogs.msdn.com/jamshedd/archive/tags/Visual+Studio/default.aspx" /></entry><entry><title>Problems while installing an update for the .NET Framework 2.0</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/jamshedd/archive/2006/10/13/Oroblems-while-installing-an-update-for-the-.NET-Framework-2-0.aspx" /><id>http://blogs.msdn.com/jamshedd/archive/2006/10/13/Oroblems-while-installing-an-update-for-the-.NET-Framework-2-0.aspx</id><published>2006-10-14T00:18:00Z</published><updated>2006-10-14T00:18:00Z</updated><content type="html">Microsoft has released a security update on Tuesday (10/10/2006) as part of the monthly patch Tuesday cycle for the .NET Framework 2.0 that addresses a vulnerability which could allow information disclosure. This security update is described in security bulletin MS06-056 and in Knowledge Base Article 922770 . A small number of users have reported issues with installing this update. It appears that the issues reported fall into 3 categories: Problem 1 The installation fails because Windows Installer...(&lt;a href="http://blogs.msdn.com/jamshedd/archive/2006/10/13/Oroblems-while-installing-an-update-for-the-.NET-Framework-2-0.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=823314" width="1" height="1"&gt;</content><author><name>jamshedd</name><uri>http://blogs.msdn.com/members/jamshedd.aspx</uri></author><category term="Security Updates" scheme="http://blogs.msdn.com/jamshedd/archive/tags/Security+Updates/default.aspx" /><category term="Security" scheme="http://blogs.msdn.com/jamshedd/archive/tags/Security/default.aspx" /></entry><entry><title>Zune</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/jamshedd/archive/2006/08/07/691705.aspx" /><id>http://blogs.msdn.com/jamshedd/archive/2006/08/07/691705.aspx</id><published>2006-08-08T05:00:00Z</published><updated>2006-08-08T05:00:00Z</updated><content type="html">Microsoft has put up a little teaser site for Zune here , allowing you to signup for notifications/emails as and when more information will be made publicly available. Is it me or is everyone wondering what the new Zune player will look like ? I definitely wonder whether Zune will it have the basic but polished appearance of the competitor's product or will it target a more geeky audience with features and buttons ? What would the storage capacity be like ? What would the screen size and resolution...(&lt;a href="http://blogs.msdn.com/jamshedd/archive/2006/08/07/691705.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=691705" width="1" height="1"&gt;</content><author><name>jamshedd</name><uri>http://blogs.msdn.com/members/jamshedd.aspx</uri></author><category term="Gadgets" scheme="http://blogs.msdn.com/jamshedd/archive/tags/Gadgets/default.aspx" /></entry><entry><title>Black Hat, Vista</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/jamshedd/archive/2006/08/05/black-hat-vista.aspx" /><id>http://blogs.msdn.com/jamshedd/archive/2006/08/05/black-hat-vista.aspx</id><published>2006-08-05T21:47:00Z</published><updated>2006-08-05T21:47:00Z</updated><content type="html">Earlier this week hackers from around the country met in Vegas at the annual Black Hat event. Vista is the first Microsoft operating system built from the ground up with security in mind i.e. using Microsoft's Secure Development Lifecycle. At Black Hat, Microsoft handed over around 3000 copies of Vista to hackers. This IMHO is fantastic for all concerned. Microsoft will have the best hackers out there poking at Vista trying to find holes in it, while the hackers have an opportunity to flex their...(&lt;a href="http://blogs.msdn.com/jamshedd/archive/2006/08/05/black-hat-vista.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=689812" width="1" height="1"&gt;</content><author><name>jamshedd</name><uri>http://blogs.msdn.com/members/jamshedd.aspx</uri></author><category term="Security" scheme="http://blogs.msdn.com/jamshedd/archive/tags/Security/default.aspx" /></entry><entry><title>whoami v2.0</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/jamshedd/archive/2006/07/27/680937.aspx" /><id>http://blogs.msdn.com/jamshedd/archive/2006/07/27/680937.aspx</id><published>2006-07-28T03:14:00Z</published><updated>2006-07-28T03:14:00Z</updated><content type="html">In my first post whoami I mentioned that that I am a PM on the DDCPX team handling the release and distribution channels. I mentioned that I took up this position to replace another team member who moved to a different team. Well, lightning does strike the same place twice sometimes. Shortly after I took on this role, another team member who was the primary Security PM for the division moved elsewhere, and I was given an opportunity which I just had to grab. Microsoft releases fixes for security...(&lt;a href="http://blogs.msdn.com/jamshedd/archive/2006/07/27/680937.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=680937" width="1" height="1"&gt;</content><author><name>jamshedd</name><uri>http://blogs.msdn.com/members/jamshedd.aspx</uri></author><category term="Servicing" scheme="http://blogs.msdn.com/jamshedd/archive/tags/Servicing/default.aspx" /><category term="Security Updates" scheme="http://blogs.msdn.com/jamshedd/archive/tags/Security+Updates/default.aspx" /></entry><entry><title>whoami</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/jamshedd/archive/2006/07/04/655826.aspx" /><id>http://blogs.msdn.com/jamshedd/archive/2006/07/04/655826.aspx</id><published>2006-07-04T11:12:00Z</published><updated>2006-07-04T11:12:00Z</updated><content type="html">I am a Program Manager in the DDCPX (Developer Division Customer Product-lifecycle Experience) team. This team services (provides regular and security updates, hotfixes, etc. for) products including Visual Studio and the .Net Framework. I have very recently stepped into the release arena, filling for another team member who moved to a different group. I own the distribution channels for the products we service. These include all the possible means for getting an update out to all our users, including...(&lt;a href="http://blogs.msdn.com/jamshedd/archive/2006/07/04/655826.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=655826" width="1" height="1"&gt;</content><author><name>jamshedd</name><uri>http://blogs.msdn.com/members/jamshedd.aspx</uri></author><category term="Servicing" scheme="http://blogs.msdn.com/jamshedd/archive/tags/Servicing/default.aspx" /><category term="Microsoft Update/Windows Update" scheme="http://blogs.msdn.com/jamshedd/archive/tags/Microsoft+Update_2F00_Windows+Update/default.aspx" /></entry><entry><title>Disclaimer</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/jamshedd/archive/2006/06/26/648128.aspx" /><id>http://blogs.msdn.com/jamshedd/archive/2006/06/26/648128.aspx</id><published>2006-06-27T07:29:00Z</published><updated>2006-06-27T07:29:00Z</updated><content type="html">The information in this weblog is provided "AS IS" with no warranties, and confers no rights. This weblog does not represent the views, thoughts, intentions, plans or strategies of my employer. It is solely my opinion. Inappropriate comments will be deleted at the authors discretion. All code samples are provided "AS IS" without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose....(&lt;a href="http://blogs.msdn.com/jamshedd/archive/2006/06/26/648128.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=648128" width="1" height="1"&gt;</content><author><name>jamshedd</name><uri>http://blogs.msdn.com/members/jamshedd.aspx</uri></author></entry></feed>