As Visual Studio 2013 Express cannot create a setup project, we downgraded to .NET Framework 3.5 and rolled back the development environment to develop on Visual Studio 2008 Pro (modified project files manually).
Actually, I would like to use Visual Studio 2013 Express, which can use .NET Framework 4.5, but I can't create a setup project with Express, and I can't use paid license libraries such as Crystal Reports, so I have no choice but to return to the old development environment.
The VS2008 Pro can create a .msi package, but the binary built in .NET 4.5 cannot be included in the environment, so I modified the code for .NET 3.5 and moved it to the VS2008 Pro environment.
By the way, the COM call, which had been working normally until now, has changed a little.
Specifically, source code of t.org/packages/WindowsAPICodePack-Core/"rel="nofollownoreferrer">Windows API Code Pack and rebuild it on the VS2008 Pro. So far, the thumbnail of the .pdf file has been displayed successfully (page 1 of the document).
Sorry for the difficulty in understanding your question.
1..Is there an installer that supports reliable .NET dependencies that can be used free of charge instead of paid installers such as Install Shield in the development of the NET Framework 4.5 (VS2013 Express)?
2. Is there an excellent free installer that can install binaries built in a VS2008 Pro environment?
3. Is there a high possibility that the .NET version of COM will go wrong?
I'm sorry, but I appreciate your cooperation.
c# visual-studio .net
Basically, it's just as Sayuri said.
In this case, I think it's the usual way to use WiX.
WiX is a compiler that writes and outputs msi execution scripts in XML, and there is also an msi decompiler called dark, so I think it would be easier to convert msi files created from existing 2008 projects into WiX XML project files and adjust them.
Geoff's Blog:Converting a Visual Studio Setup Project to Wix
http://geoffwebbercross.blogspot.jp/2012/11/converting-visual-studio-setup-project.html
Basically, I think it's best to use the WiX above, but the WiX itself has to edit the project files in detail (and that's why it's possible to do a lot of things primitively).But) it takes time and effort.
To be honest, if you convert your time and effort into mikacolove's hourly wage, I think it would be most efficient to purchase a VS2013 Pro license and utilize Microsoft Visual Studio Installer Projects VS expansion.
I think it's hard to think of simply relying on .NET's version.I think it may be an environment-dependent issue like Sayuri mentioned, or a problem that depends on the calling path around Thumbnail retrieval that is said to have used the Windows API Code Pack.
© 2024 OneMinuteCode. All rights reserved.