Using ironscheme in visual studio 2008 - visual-studio

Though it says on the IronScheme codeplex site that a plugin is included for visual studio, I have no idea how to get ironscheme working with VS...
Is it possible? If so , how?
Thanks

Firstly, you definitely need Visual Studio 2008 SP1, without SP1 it will cause problems.
Secondly, follow the instructions in the visual-studio.txt file.
Run from the command line:
If admin: RegPkg /codebase <absolute path of IronScheme.VisualStudio.dll>
If not admin: RegPkg /ranu /codebase <absolute path of IronScheme.VisualStudio.dll>
devenv /setup
Now start VS, and open a file with a 'ss' or 'sls' or 'scm' extension.
Cheers
leppie

Related

PackageId:Microsoft.VisualStudio.Setup.WMIProvider;PackageAction:Install;ReturnCode:1722;

I am trying to install Visual Studio 2019. But It gives this error:
PackageId:Microsoft.VisualStudio.Setup.WMIProvider;PackageAction:Install;ReturnCode:1722;
How can I fix this error?
Thanks
Finally I installed Visual Studio 2019 community edition.
It was about installation driver issue.
So double check regedit HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion default installation path for windows application.
So I mean my ProgramW6432Dir's value was only C:\. I changed it to C:\Program Files
check regedit
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion
default installation drivers paths. If it is not correct fix it.
Restart the windows OS.
Uninstall Visual Studio Installer and Visual Studio 2019.
Retry installation process.
For me, one of these answers helped: https://developercommunity.visualstudio.com/content/problem/1038410/packageidmicrosoftvisualstudiosetupwmiproviderpack-11.html
The one with putting in msiexec at the command prompt. You may have to change the version number, though.

The "GetReferenceNearestTargetFrameworkTask" task was not found

I have a problem with autocompletion in VS 2017 Community.
Previously I had VS 2017 Enterprise from school, but the key expired so I moved to Community.
Before, everything works great, but now it doesn't work at all.
I found a solution on Stack Overflow here but it doesn't work, so found another solution at GitHub here.
And I got this:
Build FAILED.
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets(1601,5): error MSB4036:
The "GetReferenceNearestTargetFrameworkTask" task was not found. Check the following:
1.) The name of the task in the project file is the same as the name of the task class.
2.) The task class is "public" and implements the Microsoft.Build.Framework.ITask interface.
3.) The task is correctly declared with in the project file, or in the *.tasks files located in the
"C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin" directory.
0 Warning(s)
1 Error(s)
Time Elapsed 00:00:00.11
Do you know what to do next?
I had the same error message but for a different problem.
So, I'm using MSBuild to automate build/deploy process for Azure Functions. Everything was working fine until I updated both Visual Studio 2017 and Visual Studio Build Tools 2017 at which point I started getting this error. To be precise I got this error only when using MSBuild, building project manually from VS was working fine.
In my case I already had everything set as per #Programmer's answer.
But as I was using MSBuild it turned out that I also had to install NuGet targets and build tasks which are part of Visual Studio Build Tools.
Follow these to fix that error. This applies to VS 2017:
Fix 1:
1.Install Nuget PackageManager from here.
2.Restart Visual Studio.
If the problem is still there, continue below
Fix 2:
1.Download and start/run the Visual Studio Installer again.
2.While the Visual Studio Installer is still running, go to the "Individual Components" tab
3.Tick the "NuGet package manager" check-box that is under "Code tools" option.
4.Click Install to install it.
Screenshot of where this is located:
That should fix the error you see in this question. Restart Visual Studio and test the auto-completion function. If it's not working, see the answers from this question as that is a whole different issue.
I was seeing this issue with msbuild 15.6.82 on a build environment that does not have VisualStudio 2017, only VS Build Tools.
Here's a PowerShell script that resolves this issue, it pretty much does the equivalent of previous answers in the VS Installer, but silently and waiting for completion.
Start-Process "C:\Program Files (x86)\Microsoft Visual Studio\Installer\vs_installer.exe" -ArgumentList 'modify --installPath "C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools" --quiet --add Microsoft.VisualStudio.Component.NuGet.BuildTools --add Microsoft.Net.Component.4.5.TargetingPack --norestart --force' -Wait -PassThru
I'm working with a headless build server on server core, resolved by installing chocolatey package choco install visualstudio2017-workload-webbuildtools from here:
https://chocolatey.org/packages?q=msbuild
I'm reporting an answer from a Microsoft techician
This usually indicates one of two things:
A failed VS installation. If that's the case, I would recommend running a repair on your VS install.
You have msbuild assemblies in the GAC. If that's the case, please ungac them.
Livar Cunha [MSFT]
I got the same problem in Visual Studio 2019, I solved it by simply install unity package

The 'Provider Package' did not load correctly

VS 2013 Professional - Version 12.0.31101.00 Update 4
All of a sudden, whenever I try to open a project (MVC project or Python project), I get:
The 'ProviderPackage' package did not load correctly.
The problem
may have been caused by a configuration change or by the installation
of another extension. You can get more information by examining the
file
'C:\Users\xxxx\AppData\Roaming\Microsoft\VisualStudio\12.0\ActivityLog.xml'.
In my AppData\Roaming, there is no 12.0 folder! In AppData\Local, there is a 12.0 folder but there is no ActivityLog.xml file.
When I ignore the message and press F5 to run, after lots of disk movement, Visual Studio simply closes and disappears.
I have repaired a few times and the exact same behavior persists.
When I try to run devenv.exe /setup or devenv.exe /resetuserdata, absolutely nothing happens. No error, no process is launched, nothing. Running devenv.exe without any parameters does launch VS.
What can be wrong? I hesitate to uninstall and reinstall if there is some other solution.
1 day later: Uninstalled VS 2013 and reinstalled, and then applied Update 4.
Problem is still the same for the MVC project: ProviderPackage did not load correctly, and when running project VS closes and disappears.
Last record in ActivityLog.xml says:
<entry>
<record>1120</record>
<time>2015/03/17 06:38:43.882</time>
<type>Error</type>
<source>VisualStudio</source>
<description>An exception was thrown during package instantiation and was caught in the package manager [ProviderPackage]</description>
<guid>{5F2E5E42-4192-4D79-A0D8-1D881E808829}</guid>
<hr>8000ffff - E_UNEXPECTED</hr>
<errorinfo></errorinfo>
</entry>
Deleting ComponentModelCache from
C:\Users\YourUserName\AppData\Local\Microsoft\VisualStudio\14.0\ComponentModelCache
works fine for VS 2015.
Note: You will need to close the VS before deleting this folder. Also replace 14.0 with 12.0 in folder path for VS 2013
Delete folder ComponenModelCache
C:\Users\XXXX\AppData\Local\Microsoft\VisualStudio\XX\ComponentModelCache
that worked for me
Open Command Prompt and use the following commands (if necessary, change the directory according to the installation folder):
cd c:\
C:\>"C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\devenv.exe" /resetskippkgs"
Make sure the paths are correct at:
Computer\HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\14.0
Mine for example the VisualStudioLocation key changed from "C:\Documents\Visual Studio 2015" to just "Visual Studio 2015" which was problematic.
I can't leave a comment on Murat Yıldız's answer so this is the next best thing. His solutions works great. I opened the Visual Studio Command Prompt as an administrator and ran from the command prompt:
C:\WINDOWS\system32>devenv /resetskippkgs
It worked like a charm.
I also faced the same problem and solution for me was to run Visual Studio as an administrator.

visual studio cannot open new project

Whenever I try to create a new project in VS 2010 I get the error:
New project/item dialog could not be initialized due to error:
Exception of type 'Microsoft.VisualStudio.Dialogs.DialogInitializationException' was thrown.
And when try to open existing project visual studio 2010 restarts.
I had the same problem on my computer. After a long time searching I solved it by the following steps:
Close all instances of Visual Studio
Go to "C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE" (or whatever is your VS installation directory)
Run command devenv.exe /resetuserdata and wait until finished
Run Visual Studio
I can't find the former case. As you met an exception
Microsoft.VisualStudio.Dialogs.DialogInitializationException
I am suggesting you try the way below:
Run devenv /resetuserdata.
Delete the file:
%LOCALAPPDATA%\Microsoft\VisualStudio\11.0\ComponentModelCache
and restart Visual Studio.
Close all VS instances and try the solution mentioned here:
Launch Developer Command Prompt for VS 2017 as Administrator
Go to VS 2017 installation folder, for example: pushd C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise
gacutil -if Common7\IDE\PublicAssemblies\Microsoft.VisualStudio.Shell.Interop.8.0.dll
Open your control panel
Change
Regional -> Formats tab -> Format: English(United States)
https://connect.microsoft.com/VisualStudio/feedback/details/727578/vs-do-not-work-with-finnish-number-format-on-w8-64-bit
It works for me :)
This problem can cause when you install an older version of Visual Studio nearby the current version. For example VS 2017 is installed on your system and you do force install of VS 2008.
I faced this problem many years ago by installing VS 2008 after VS 2010;
and today again I had this problem. Because I installed SolidWorks 2015 after VS 2017. SolidWorks had a Visual Studio 2008 inside its package that interferes my installation.
Just uninstalled VS 2008 and I'm done.
I found this to still be an issue in Visual Studio Community 2017, Microsoft released a work around that fixed my problem:
The work-around for this issue would be:
-Launch “Developer Command Prompt for VS 2017” as Administrator
-Go to VS 2017 installation folder, for example: pushd C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise
-gacutil -if Common7\IDE\PublicAssemblies\Microsoft.VisualStudio.Shell.Interop.8.0.dll

Visual Studio 2008 ProjectTemplates

Is there anywhere I can download the ProjectTemplates folder for Visual Studio 2008? I accidently deleted it and the cache folder so need to get a copy of it!
What about using installation repair?
Try running this from the Visual Studio Command Prompt. It should allow you to fix the problem without going through the installation repair process.
devenv /installvstemplates

Resources