>The thread mentioned that the only way to get the patch is through PSS.
With
>my MSDN subscription I don't have access to PSS, and can't seem to locate
>the patch on MSDN.

""Gary Chang[MSFT]"" <v-garych@online.microsoft.com> wrote in message
news:ENyPdMeiFHA.944@TK2MSFTNGXA01.phx.gbl...
> Hi Chuck,
>
>>The thread mentioned that the only way to get the patch is through PSS.
> With
>>my MSDN subscription I don't have access to PSS, and can't seem to locate
>>the patch on MSDN.
>
> yes, currently this patch is not available in the MSDN website, so this
> may
> need you submit a support incident in Microsoft PSS (Product Support
> Service)to request that patch. As a MSDN subscriber, you have two free
> support incidents.
>
> And if the problem is confirmed by Microsoft PSS as a product issue, PSS
> won't charge money. Every MSDN subscriber has two free support incidents.
> You could use one of them to contact Microsoft PSS. So you don't need to
> pay money yet. Surely if the issue is a product issue, you still have two
> free support incidents.
>
> For your reference, I attached steps to contact Microsoft PSS here: You
> can
> contact Microsoft Product Support directly to discuss additional support
> options you may have available, by contacting us at 1-(800)936-5800 or by
> choosing one of the options listed at
> http://support.microsoft.com/d-efault.aspx?scid=fh;EN-US;Offe-rProPhone
>
> By the way, when you contact PSS for this patch, you may need to tell us
> the related KB article number about it, since we don't have a related KB
> article on this issue, you may tell them a corresponding resolved
> supporting case information:
>
> Case Number: SRZ041011001095
> Title: Obtain Visual Studio.NET websetup fix/enhancement ()
>
>
> Thanks!
>
> Best regards,
>
> Gary Chang
> Microsoft Community Support
> --------------------
> Get Secure! ¡§C www.microsoft.com/security
> Register to Access MSDN Managed Newsgroups!
> http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
> &SD=msdn
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>

>I called the number you listed, and they cannot locate a case
>with that number. Is there another case ID to look for?

>Also, I'm curious why this hotfix isn't available via MSDN--It sure
>save a lot of trouble. Do you know why?

""Gary Chang[MSFT]"" <v-garych@online.microsoft.com> wrote in message
news:FGsUI3ZjFHA.944@TK2MSFTNGXA01.phx.gbl...
> Hi Chuck,
>
>>I called the number you listed, and they cannot locate a case
>>with that number. Is there another case ID to look for?
>
> In this scenario, you may try to download this fix package from somewhere
> else:
> http://www.greenmartian.net/files/websetupfix.zip
>
> And please refer to the following steps to patch it:
>
> 1. Extract the Websetupfix.zip file
> 2. Copy the DPCA.DLL file over the existing DPCA.DLL at
> <vsinstall>\Common7\Tools\Deployment\DPCA.DLL
> 3. Open Visual Studio .Net
> 4. Build the Visual Studio Setup & Deployment Package
> 5.Place EnableHostHeaders.js script in the same directory with the
> Microsoft Windows Installer 2.0 Package (MSI)
> 6. Run the EnableHostHeaders.js script with one command-line argument
> Note: EnableHostHeaders <filename of the msi>
> 7. Rebuild the Microsoft Visual Studio .Net Setup & Deployment Web
> Application
> 8. You will notice a drop down list that will allow you to select where
> you
> would like to install.
>
>
>>Also, I'm curious why this hotfix isn't available via MSDN--It sure
>>save a lot of trouble. Do you know why?
>
> Except some urgent Windows's system's hotfix, our products' hotfix is only
> available from the PSS, the general convention is to contact PSS to
> request
> a specific hotfix. And in this case, since the Websetupfix.zip hotfix
> hasn't been released publicly yet, so we don't have a related KB about
> it...
>
>
> Hope this helps!
>
> Best regards,
>
> Gary Chang
> Microsoft Community Support
> --------------------
> Get Secure! ¡§C www.microsoft.com/security
> Register to Access MSDN Managed Newsgroups!
> http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
> &SD=msdn
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>

"Yan-Hong Huang[MSFT]" <yhhuang@online.microsoft.com> wrote in message
news:GaMS$UojFHA.2700@TK2MSFTNGXA01.phx.gbl...
> Hi Chunk,
>
> For question 2:
> The answer is that we are trying to do the right thing. If you have any
> specific concerns regarding calling PSS for a fix versus downloading them
> from a web site I would be happy to pass them on.
>
> As far as when these fixes will be widely distributed, every QFE that we
> ship is considered for the next available service pack. Some QFEs can't be
> included in a service pack They may contain breaking changes that only
> make
> sense for the customer that originally requested the QFE for example. So
> every hotfix request needs to go through PSS now. We will keep monitoring
> the usage of them to better improve the product.
>
> Thanks very much for your understanding.
>
> Best regards,
> Yanhong Huang
> Microsoft Community Support
>
> Get Secure! ¨C www.microsoft.com/security
> Register to Access MSDN Managed Newsgroups!
> -http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.as
> p&SD=msdn
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>

>Perhaps I read the original threads incorrectly, but I thought
>the modification would allow the user to choose the physical
>directory for the install, instead it only allows a choice of the
>web site. Is there a similar change (or script that could be used)
>to allow install into a specific path?

>The biggest specific concern is that as an MSDN subscriber,
> I can't call PSS to get the fix. I can download from the web site
>if it's available.