Home Dashboard Directory Help
Search

VS 2010 Setup Project by Yatish Ram


Status: 

Closed
 as Won't Fix Help for as Won't Fix


7
0
Sign in
to vote
Type: Bug
ID: 588640
Opened: 8/24/2010 3:58:13 AM
Access Restriction: Public
0
Workaround(s)
view
6
User(s) can reproduce this bug

Description

We have recently migrated to VS 2010 from VS2008. Our application is targeted for Windows 2000 host. The setup project (MSI) built with VS2008 used to install fine on Win2000 box, but the new MSIs built by VS2010 doesn't install on Win2000, it installs fine on XP box though.

i didn't find any such things that MSIs won't work on old OS, I know officialy support for 2000 has ended. Any thoughts on the same?

The target framework of the MSI is set to Framework 2.0. MSI builds fine without any warning or error, when installing it on Windows 2000; it stops with the message "The installer was interrupted before [Setup name] could be installed. You need to restart the installer to try again."

Even if I log the verbose out put of MSI execution, it doesn't say anything except for DIRCA_CheckFX returns the value 3, which means it fails the framework check.

The project targets only Framework 2.0 throughout, and the same MSI installs fine, when built with VS2008, but it doesn't when built with VS2010

The Windows 2000 system is with service pack 4. Project prerequisite and launch condition are all set to framework 2.0. There is some difference though how Visual studio displays it. VS2008 display it as 2.0.50727 in the dropdown, and VS2010 display it as Framework 2.0 in the same dropdown.

If you open the built MSIs (one built by VS2008, and the one built by VS2010) using ORCA, there is definitely the difference there. The same MSI installs on the same machine when built with VS2008, and doesn't work when built with VS2010
Details
Sign in to post a comment.
Posted by Yatish Ram on 10/8/2010 at 2:17 AM
Great!!
I am thinking, why I logged this issue in first place, looking at the history of professionalism that Microsoft shows in such cases.
It is easy for you to say, you don't have time. You should test you products before releasing them in the market. Why do you guys release new version of products when they don't even have the existing functionality?

Thanks for updating this thread, 'Yes, we know it is a bug, but won't fix it!'
Posted by Microsoft on 10/7/2010 at 4:21 PM
Hi,

Thank you for reporting this issue. Although we are able to reproduce this problem, it is unfortunate that we do not have time to address this request. Since W2K is no longer a supported OS platform, we antipicate the number of customers hitting this issue will be low. While at times we may not be able to get to them (such as in this case), please continue to log your suggestions and issues as they play an important part in helping us understand what customers want.

Please let us know if you have any concerns within 7 days.

Thank you.
Posted by Paritosh Arya on 9/24/2010 at 1:31 PM
I am hitting my head against the wall with this bug.

Didn't expected no-reply from Microsoft...the same issue is holding us back.

When is someone going to get this fixed!!!
Posted by Scott_2010 on 9/20/2010 at 10:07 AM
Any word on this yet? We're having this same issue for production releases... YIKES
Posted by Yatish Ram on 9/17/2010 at 2:27 AM
Ok I didn't say it was urgent, but does that mean u'll never update this thread. I raised this issue around a month back and still, there is no update on this.
Can any one please update tit, or shall I forget it completely?
Posted by ChrisHorak on 9/9/2010 at 12:49 AM
We are seeing exactly the same issue. Is there a workaround for this?

Thanks
Chris
Posted by Microsoft on 8/24/2010 at 11:14 PM
Thank you for reporting the issue.
We are routing this issue to the appropriate group within the Visual Studio Product Team for triage and resolution.These specialized experts will follow-up with your issue.
Posted by Microsoft on 8/24/2010 at 5:03 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.