Nothing happens when creating a new project in VS2017 on Windows 7 - visual-studio-2017

When I try to create a new project in VS2017 , I select my template and click OK
Nothing happens.
This issue started recently and the problem does not occur if I am running as administrator.
So far I am investigating this link on registry issues
I found the advice "Unfortunately the current work-around is to export settings / delete the private registry file / import settings and try again."

Huy Nguyen gives the answer at
https://developercommunity.visualstudio.com/content/problem/79829/access-denied-when-trying-to-enableinstall-an-exte.html
Export your current VS settings with Tools | Import and Export Settings… because the next step will lose custom settings and extensions
(If the registry is corrupted, export settings may fail and we have to ignore this step)
Delete VS app data: %LocalAppData%\Microsoft\VisualStudio\15.0_[UniqueID].
If your account is part of the Administrators group, launch Visual Studio as Administrator once. You can continue to run as Standard User afterwards.
Otherwise, launch Visual Studio as Standard User.

Related

use devenv to generate ispac with EncryptSensitiveWithPassword

We have an external app that allow use to build and deploy ssis projects using command tool
after a migration with vs 2019, process no longer work (probably because external app use old resource file)
previously, we use msbuild, with a xxx.proj using
UsingTask TaskName="DeploymentFileCompilerTask" AssemblyFile="C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies\Microsoft.SqlServer.IntegrationServices.Build.dll"
now, the same no longer work. I tried to use a newer version of Microsoft.SqlServer.IntegrationServices.Build.dll but it refer now to an vsintegration dll file.
So, I would like to use devenv.com tool instead.In local, it works.
the problem is that some projects have SecurityLevel to EncryptSensitiveWithPassword and when using
devenv.com "project.sln" /Build Development /Project "project\SsisCommon.dtproj" /ProjectConfig Development
in local, it prompt for the project password, and then after entered it, it generate ispac.
But the problem is that the external app not allow prompting, and then we got this kind of error
Unhandled Exception: System.InvalidOperationException: Showing a modal dialog box or form when the application is not running in UserInteractive mode is not a valid operation. Specify the ServiceNotification or DefaultDesktopOnly style to display a notification from a service application.
How I can pass the project password without prompting ?
thanks in advance
regards
I finally use the SSISBuild project - https://github.com/rtumaykin/ssis-build/ - (recompiling after updating encrypt / decrypt process) as related here: https://github.com/rtumaykin/ssis-build/issues/25
it works finally fine.
regards

Why does the setting "MSBuild project build output verbosity" have no effect?

I am having trouble finding relevant messages in a myriad of MSBuild output. It seems like a problem with my Visual Studio configuration: the build output verbosity behaves as if it is set to "Detailed", independent from what I have set in Tools → Options → Projects and Solutions → Build and Run → MSBuild project build output verbosity.
The issue is reproducable with a default C++ console application project:
The screenshot shows the application, the ouput verbosity settings and the unexpected output in the "Output" window.
I came across this problem in another project that has a significantly longer build time. When I open the settings window while the project is building, I can see that the setting has reset to "Detailed"
Do you have any idea why the setting does not have an effect or why it is overridden?
As written, the problem is project-independent and seems like an issue with my configuration. I already tried deleting the settings in %USERPROFILE%\AppData\Local\Microsoft\VisualStudio\... and %USERPROFILE%\AppData\Roaming\Microsoft\VisualStudio\...
but Visual Studio manages to restore the settings from some history:
Are you using the same account to sign in vs on different computers? Maybe this cause the problem.
You can try to reset all settings under Tools > Import and Export Settings and try it again.

VS2015 Debugger is not expanding variables

When I debug a c++ application, I am unable to see the value of the variable
If you see below,
std::string s = "a";
The debugger only shows the value as {...}, even if I extend the value.
What I have tried
Deleted the symbol cache, (Tools > Options ... > Debugging > Symbols.
Unchecked "Use Managed Compatibility mode"
Checked "Use Managed Compatibility Mode"
Unchecked "Use Native Compatibility Mode"
Checked "Use Native Compatibility Mode"
I have tried to export the settings from the working environment and then import them into the other one, with no luck.
Any suggestions? ...
I get the same issue with std::vector<std::string> ... or any other type, I cannot expand the data.
Edit: Added a picture of what it is supposed to look like ...
Edit 2: I have tried to export the settings from the working environment and then import them into the other one, with no luck.
To fix the issue I un-installed VS2015 completely, (including all the updates and other "vs2015" tools that were installed over the months.
I then ran ccleaner a couple of times to remove dead registry settings left behind, (not sure if that helped, but it doesn't hurt).
I than re-ran the install, it picked up that update 3 was needed.
A couple of things were not removed as I didn't need to re-register and enter my credentials.
But it seems it wasn't the problem as the re-install did the trick.
Also:
Unchecked "Use Managed Compatibility mode"
Unchecked "Use Native Compatibility Mode"

Can't get past Microsoft.VisualStudio.MinShell.Msi.msi in VS2017 RC Update

I previously successfully installed Visual Studio 2017 RC Enterprise on Windows 10 Home. I saw in the Notifications area an update to a later version of the RC, and so I clicked on that notification to install it.
The installation got as far as the attempting to install the Android Emulators, but failed and the log said it needed Win10 Pro.
So I removed the emulator from the install options, but the install didn't complete and this time the log said:
[27ac:0038][2017-01-31T10:08:47] Download requested: https://download.microsoft.com/download/8/7/A/87AEAAB0-D624-400E-899E-61FAFAE42BA5/Microsoft.VisualStudio.MinShell.Interop.Msi.msi
[27ac:003a][2017-01-31T10:08:47] Attempting download 'https://download.microsoft.com/download/8/7/A/87AEAAB0-D624-400E-899E-61FAFAE42BA5/Microsoft.VisualStudio.MinShell.Interop.Msi.msi' using engine 'WebClient'
[27ac:0026][2017-01-31T10:08:48] Completed: Installing Microsoft.VisualStudio.MinShell.Msi
[27ac:0026][2017-01-31T10:08:48] Error: Package 'Microsoft.VisualStudio.MinShell.Msi,version=15.0.26109.1' failed to install. MSI: C:\ProgramData\Microsoft\VisualStudio\Packages\Microsoft.VisualStudio.MinShell.Msi,version=15.0.26109.1\Microsoft.VisualStudio.MinShell.Msi.msi, Properties: REBOOT=ReallySuppress ARPSYSTEMCOMPONENT=1 MSIFASTINSTALL="7" VSEXTUI="1" VS7.3643236F_FC70_11D3_A536_0090278A1BB8="C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise" , Return code: 1316, Details: The specified account already exists.
I tried to follow the instructions from Visual Studio 2017 RC Install Error "The specified account already exists." however its says the action is only valid for installed products
Yesterday I did notice MinShell in the Programmes Uninstall list and tried removing it from there.
However it makes no difference and every time I try and run the installer I get the same error. I have tried making sure that no VS2017 related items are installed in Programs and Features, and deleting directories manually from Program files etc
Starting to get really annoyed as I had a completely working compiler and IDE and I've already been totally unable to upgrade Win10 to the Anniversary Update due to the 0x8007002C – 0x400D error during Migrate-Data operation. I tried the fix of resetting the Storage app to make all defaults C:, and then the Documents link, but that didn't fix it, although I see I've missed Downloads, Pictures and Video, so will try again tonight but I still don't see it working, although I think the failure moved from 79% to 83%
#Peter Nimmo I had the same issue. Solve it by:
Go to C:\Program Data\Microsoft, go to Properties then click the Security tab and add System, then give full permission. The reason why it couldn't install is because it can't access the folder required.
Hope it works for you. If it doesn't, you could try the following additional steps:
Go to C:\ then at the search box type %temp% then delete everything in it.
Run this script in Powershell Admin mode: https://gist.github.com/heaths/77fbe0b44496960fab25c2eb0b9e8475.
This problem might be caused by setting a separate cache folder when installing. The steps below should fix it.
delete the visualstudio folder in your Registry editor HKEY_LOCAL_MACHINE\SOFTWARE(under Microsoft?)
run InstallCleanup.exe---> C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\layout
delete contents in your temp folder C:\Users\yourusername\AppData\Local\Temp(skip items that cannot be deleted)
run InstallCleanup.exe
inside C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\layout
then restart your computer
Go to %ProgramData%\Microsoft and rename VisualStudio folder (e.g. to VisualStudio_old)
Try again with fresh install.
Please temporarily disable 3rd party anti-virus software and try the following steps to check if it works for you:
Type “Administrative Tools” in search box
Open “Local Security Policy”
Navigate to “Software Restriction Policies” (If it displays “No Software Restrictions Defined”, please right-click on the “Software Restriction Policies” node and select “New Software Restriction Policies”)
Double-click on “Enforcement”
Select “All users except Local Administrators” and click on OK
Restart your computer and run the Visual Studio Installer as administrator to repair the installation
Please Refer : https://learn.microsoft.com/en-us/answers/questions/147767/visual-studio-2019-can39t-install-microsoftvisuals.html
similar error for me sort of, it starts installing then gets stuck on shell(minimum) and shell interops and the shell(minimum) resources and interop resources..then i get a fatal error, tells me that Visual Studio Devenv resource fails.. no matter what i try i cannot install on my windows 10 1607 anniversary update 3 64-bit with all updates to this minute. I read microsoft is aware and its become a huge problem, programming error. Anyone figures out how to install let me know please.
EDIT: so its a huge pain to get visual studio 2015 to install, i kept reinstalling it and everytime the error window came up i read the log, then i manually searched and installed components listed, and also had to manually create folders almost each time following the path listed in the log file. after 12 hours and alot of searching and installing i now have a fully functional visual studio 2015 pro edition back on my computer..i wanted 2017 but thats even worse to install..lol..

Set app to require elevation?

I'm working on the bootstrap application of a new installer for some of our products. So far, I've been relying on two things that I read about somewhere:
Applications whose name contains "setup" or "install" will run elevated by default.
Applications that run elevated will launch other applications in elevated mode.
Recent testing has found that one or both of these statements is false, because one of the applications that I'm launching is a third party installer that requires elevation, and it's failing because of the elevation requirement.
How do I set my application to require elevation? I know it has something to do with the manifest file. As I'm working in Visual Studio 2008, and the manifest file is generated, I'd like to know what to enter into the project's properties and where to make it require elevation.
When I couldn't find application manifest as a new item that could be added to my project, I went into the online help and found this:
configure the VS2008 in Configuration Properties - Linker - Manifest File - UAC Execution Level (requireAdministrator)
That did the trick.
In VS2008: Add new item; application manifest file (app.manifest; the comments in the template file tell you how to demand more access).
You can now specify the manifest in project properties on the Application tab (but you need to uncheck "Enable the Visual Studio hosting process" to debug it).