I'm working with installshield 2013 limited edition in visual studio 2012. This used to work fine on windows 8.1. After upgrading to windows 10 installshield produces a BSOD: registry_filter_driver_exception; ISRegFlt64.sys problem.
This is a known problem for Flexera but they don't seem to offer an upgrade.
Or am I missing something?
The fix is present in InstallShield 2015, including the 2015 Limited Edition. If you can't use that because of editions of Visual Studio, you should be able to just take the updated driver and replace it per (tweaked) instructions on the community (except for the bug fix, the driver is shared and hasn't changed lately):
... copy ISRegFlt.sys (ISRegFlt64.sys on 64-bit machines) from \Program Files (x86)\InstallShield\2015\System to the System folders of any other recent versions of [InstallShield] on the machine.
Related
For InstallScript projects, does anyone know why InstallShield 2012 returns 6.2 in the SYSINFO values for Windows 8.1 and Windows 2012 R2 which should be returning 6.3? Specifically in the SYSINFO.nOSMajor and SYSINFO.nOSMinor versions numbers.
If this is simply a bug in InstallShield are there any other ways to detect the OS version number?
See the InstallShield community thread Installscript Project - Target machine setting recognizing Windows 8.1 as Windows 8. Note that there are two downloads referenced:
Updated manifest files so that Windows's compatibility shims don't interfere; this can be applied to any recent version of InstallShield.
A fix for a bug that the first revealed in InstallShield 2013; this doesn't affect previous versions that lack explicit support for Windows 8.1, and should only be applied to InstallShield 2013.
I am wondering how we are suppose to use the remote debugger on a target machine with Windows XP for applications build using Visual Studio 2013.
It seems that Remote Debug Tools for Microsoft Visual Studio 2013 (and 2012) do not install on Windows XP, complaining that they need a newer Windows version. Microsoft download do not say a thing about requirements.
I guess there should be a way of doing it...
Here is the document on Visual Studio 2013 Compatibility and it does state that Remote Debugging and profiling tools are not available for the targeted platforms of XP and Vista.
Most likely the reason that the Remote Tools for Visual Studio 2012 and 2013 do not run on XP is that XP does not support .NET 4.5.
Target your app for .NET 4 so you can run it on the XP platform, and use Visual Studio 2013 to do the majority of the coding and then use Visual Studio 2010 to do the remote debugging when needed. VS 2010 and 2013 can run side by side and the project formats are compatible so you should be able to go back and forth very easily.
I am trying to build a project using WDK 8.1 and Visual Studio 2012 under Windows 8. I do not have Visual Studio 2013 Preview installed, however according to the requirements page I have fulfilled all the requirements:
WDK 8.1 Requirements
That page says:
System Requirements Before you install the WDK, you must first install
Microsoft Visual Studio Professional 2012 or above.
My project was created using WDK 8.0 so I followed the instructions provided here for migrating to WDK 8.1:
ProjectUpgradeTool: Upgrade a WDK 8 project or solution to WDK 8.1
While running the command:
ProjectUpgradeTool.exe C:\Sources\MyDriver
I got the following error:
Catastrophic failure while converting projects under
'C:\Sources\MyDriver': Message:Could not load file or assembly
'Microsoft.Build, Version=12.0.0.0 , Culture=neutral,
PublicKeyToken=b03f5f7f11d50a3a' or one of its dependenc ies. The
system cannot find the file specified.
StackTrace=
at Microsoft.DriverKit.ProjectUpgradeTool.ProjectUpgrader.UpgradeProjec
ts(IEnumerable1 projectFiles)
at Microsoft.DriverKit.ProjectUpgradeTool.Upgrader.UpgradeProjects(IEnu
merable1 files, String newOsConfigName)
Does anyone have a hint on how to get around this error?
Update as of Jan 12 2014
The documentation has been modified since I posted this question, and it clearly states now that VS2013 is indeed required for WDK8.1 development.
Same question in MSDN forums
If you want to use WDK with Visual Studio 2012, you should get not 8.1 version but 8.0 of WDK.
The first item in the system requirements on the page that you have linked to clearly states that Visual Studio 2013 is required to use WDK 8.1:
Before you install WDK 8.1, you must first install Visual Studio 2013.
You will need to keep using WDK 8 with Visual Studio 2012, although it's not officially supported any more:
We provide Windows Driver Kit (WDK) 8 to give you time to migrate to
WDK 8.1 and Visual Studio 2013. Microsoft does not support WDK 8 and
will make no further updates to WDK 8. We recommend that you use the
latest versions of the WDK and Visual Studio to build drivers for
Windows. Download the Windows Driver Kit (WDK) 8, which has tools to
build, test, debug, and deploy drivers.
You need Visual Studio 2013 to develop for Windows 8.1 I believe.
If you have both WDK 8.0 and 8.1 installed, the active one is specified using %WDKContentRoot% env var. Your vcxproj likely references the WDK by this variable so may have to change it.
I want to compile next line:
R"(The String Data \ Stuff " )"
When target is windows XP (vc110_xp), it gives me compilation error; if the VC++ target is not Windows XP, compiler accepts the syntax.
¿Why?
The November 2012 Compiler CTP is a community technology preview: it's a preview for people to use and test with, but is not intended for production use (it does not come with a "Go Live" license).
Visual Studio 2012 Update 1 is an update for Visual Studio 2012 that is intended for production use. This is the update that includes support for using Visual C++ 2012 to target Windows XP.
These are two different releases, made for two different purposes. The November 2012 Compiler CTP was released before Visual Studio 2012 Update 1 was released, and it does not include the support for Windows XP (it only updates the compiler binaries, though, so you might be able to use some MSBuild magic to use the new preview compiler with the new Windows XP support libraries; doing so is not supported, though).
If I've installed the Visual Studio 2012, do I need to install the Windows SDK, or are all tools / parts of the SDK included as part of the Visual Studio installation.
The visual studio 2012 installer does not contain the full Windows SDK or Visual Studio 2012 SDK. these need to be installed separately.
Depends on which version of VS 2012 you have installed. Professional version and above include the Windows 8 SDK, so unless you are planning to develop applications for Windows XP or earlier versions of the OS, there is no need to install the SDK separately - you would already have it.
However, if you have installed VS 2012 Express, I would suggest referring to on-line documentation for clarification on this issue.
See this post for more information:
http://blogs.msdn.com/b/chuckw/archive/2012/03/22/where-is-the-directx-sdk.aspx
"The DirectX SDK is now part of the Windows 8.0 SDK."
"The Windows SDK for Windows 8 (aka Windows 8.0 SDK) is included with Visual Studio 2012, and is also available as a standalone package for use with Visual Studio 2010."