|
-
Jun 20th, 2005, 07:28 PM
#1
Thread Starter
Fanatic Member
Vb setup version conflict
Hi,
i am using Package and Deployment wizard.....i created a setup in windows 2k pc(service pack 4).......and tried to install in windows xp pc....but i am getting error somefiles are older and the setup quits........how can i rtesolve this?
thanks
vivek.s
-
Jun 20th, 2005, 07:44 PM
#2
Re: Vb setup version conflict
This is a known issue with the P&D wiz. There was a link to the microsoft knowledge base article in this forum a while ago. It has the
workaround for it in the thread.
VB/Office Guru™ (AKA: Gangsta Yoda™ ®)
I dont answer coding questions via PM. Please post a thread in the appropriate forum. 
Microsoft MVP 2006-2011
Office Development FAQ (C#, VB.NET, VB 6, VBA)
Senior Jedi Software Engineer MCP (VB 6 & .NET), BSEE, CET
If a post has helped you then Please Rate it! 
• Reps & Rating Posts • VS.NET on Vista • Multiple .NET Framework Versions • Office Primary Interop Assemblies • VB/Office Guru™ Word SpellChecker™.NET • VB/Office Guru™ Word SpellChecker™ VB6 • VB.NET Attributes Ex. • Outlook Global Address List • API Viewer utility • .NET API Viewer Utility •
System: Intel i7 6850K, Geforce GTX1060, Samsung M.2 1 TB & SATA 500 GB, 32 GBs DDR4 3300 Quad Channel RAM, 2 Viewsonic 24" LCDs, Windows 10, Office 2016, VS 2019, VB6 SP6 
-
Jun 21st, 2005, 03:47 PM
#3
Thread Starter
Fanatic Member
Re: Vb setup version conflict
Hi Guru,
I searched but wasnt able to spot it out........wud you be able to provide me the link when u find time?
Thanks a lot!
Regards
Vivek.S
-
Jun 22nd, 2005, 10:50 AM
#4
Re: Vb setup version conflict
vivek, this may not be what you want to hear, but the PDW is NOT a good installer, MS knows this and has for a long time. There are other installers you can use including free ones (like INNO)
If you REALLY REALLY want to use the PDW then we can try to help you, but I tell everyone to avoid it. It is well known for including files that will screw up someone elses system if isntalled on it and have version conflicts like the problem you are having.
I once compiled a VB6 app using PDW in windows XP, and gave it to someone on a 98 machine, and it had included the MSVCRT file (MS Virtual C Run Time) which totally bombed out the 98 machine until i could get a 98 version of that file to put back on his system (he was not happy)
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|