FxCop folder missing - fxcop

What is the issue?
I am trying to install FxCop 10. To install that, Microsoft Windows SDK 7.1 is required. I installed the SDK. Now, to install FxCop, I have to run FxCopSetup.exe, which is supposed to be located in the folder %ProgramFiles%\Microsoft SDKs\Windows\v7.1\Bin\FxCop. But, that folder is missing.
What I did to try to fix it?
I searched the web to fix the issue, and I tried a couple of workarounds that were suggested in a few discussions including (1) not doing a full installation of the SDK and (2) uninstall SDK, reboot, re-install SDK and reboot.
Any help is greatly appreciated. Thanks!
Btw, I'm running Windows 7 (if that's relevant).

In my SDK install, there is an FXCop folder: C:\Program Files\Microsoft SDKs\Windows\v7.0A\FXCop. Is there an FxCop folder somewhere in you SDK install? Apparently it's been moved...
Alternately, I have the FxCop installer on my Dropbox: http://dl.dropbox.com/u/1311259/FxCopSetup-10.0.exe

It's in Program Files, not Program Files(x86). I realized this when running a repair on the windows sdk when I couldn't find the folder, and seeing where it was copying files.

It worked for me when I only selected the "Tools" option to install.

Related

All my JetBrains can't launch with IDEA.exe (no response when clicking), but it could launch through idea.pat

I click IDEA.64 and there is no response. However, when I click idea.pat, it could launch. I am very confused. I tried to uninstall and install again, but it doesn't work. Also, my Clion has the same issue.
The answer from JB's community by Konstantin Annikov :
'Please install https://aka.ms/vs/16/release/vc_redist.x64.exe. The root cause is that vcruntime140.dll from Visual C++ Redistributable package failed to load. It is one of jbr\bin\awt.dll dependencies. Visual Studio makes changes to C++ tools sometimes and we are working on including this dll into IDE installation, or exclude its functionality.C++ tools are needed to run IntelliJ IDEA'

mod_auth_openidc build steps on windows 64bit

I am trying to compile mod_auth_openidc module on windows 7 64bit os
I got source code from
Source Code from github
I tried to build this module using visual studio 2015 but it was throwing an error "You must use GNU compiler".
From last few days am trying to build this in windows but ...
Could you please help me to build this module in windows or if any one done this in windows can you please share build steps.
Thanks...
It would be best to download the binary that is compiled for Windows from the release page but if you insist you can follow the guidelines from: http://wgsnetman.blogspot.nl/2013/04/building-apache-244-from-unix-source.html with a lot of adaptations/workarounds...
The code for mod_auth_openidc was forked to this git repository https://github.com/dematic-spe/mod_auth_openidc.
The build steps as documented on that page are:
bootstrap-windows.cmd
build.cmd - the output is in the tartet folder. The output is two zip files, one for x86 and one for x64.
deploy_to_artifactory.cmd
There were a couple of minor edits to the code so that it would also compile for win32 as well. It used the microsoft vcpkg project which is great at compiling a lot of opensource code for windows. I tested it all with VC2019.

How to install a home made dll in order it is found by wine?

I am developping a multi-platform application under Linux. To build the Windows versions, I make use of cross-compiling with MinGW. For "first" tests, I am using wine. First, I have started with MinGW32 and wine configured for Windows XP.
I need to build tier dll and my own dll. Build is alright. If I copy them in C:\windows\system32\ and run my application which use these dll under wine, it does not find them. If I put a copy of the dll in the same directory than the application, it works.
I have tried :
~/.wine/drive_c/windows/system32/
/root/.wine/drive_c/windows/system32/
If I run the explorer (wine explorer), and browse into C:\windows\system32\ , my dll are not there !
Thus, how can I make wine find home made dlls ? I have had a look at winecfg and winetricks, but they are of no help.
Cheers,
Laurent.
Try creating an installer for your application, using nsis or something, and creating a package that includes your dll and application. Then install that installer using wine.

change clickonce install path

I deployed a project via ClickOnce cause I like the update features, but after install on some systems its hard to find.
On windows Vista and Windows 7, you will find the ClickOnce cache here: c:\users\username\AppData\Local\Apps\2.0\obfuscatedfoldername\obfuscatedfoldername
On Windows XP, you will find it here: C:\Documents and Settings\username\LocalSettings\Apps\2.0\obfuscatedfoldername\obfuscatedfoldername
Is it possible to change the path of an application installed via ClickOnce? I've looked in the publish settings and don't see a way to change the default path. Am I missing something?
No, that's beyond the scope of a ClickOnce install.
Why don't you distribute your updates through the ClickOnce system?

Qt application is not installed on other system, except the system where build was made

I have made an application using Qt 5.0.2 and made its build using inno setup. The application is successfully installed and launched at my system and worked fine.But when i installed it on other system, application is not installing or launching also no error showing. Please help me guys... What to do
If you are using visual studio to build your application you will probably need to install vcredist_sp1_x86.exe on the destination machine. You can find it somewhere in the installation folder of Qt. You can add it to the list of files in the Inno script, and add entry in the [Run] section. Also make sure you have included in your setup script:
Qt5Core.dll
Qt5Gui.dll
Qt5Widgets.dll
libGLESv2.dll
icuuc49.dll
icuin49.dll
icudt49.dll
D3DCompiler_43.dll
plugins/platforms/qwindows.dll ->should be installed in platforms/qwindows.dll in the destination folder. The same applies to imageformats plugins if you use them.
If you think there are too much dlls you will need to rebuild Qt with other configuration options, but that's another story...