I get error "Object reference not set to an instance of an object" as soon as I try to access solution properties in Visual Studio 2012. It can be temporally solved by uninstalling Nuget, which is described here: Visual Studio - Error when clicking on Solution -> Properties (Object reference not set to an instance of an object)
If I uninstall NuGet it starts working fine, but as soon as I add NuGet back again same issue occurs again immediately. Nuget update to new version did not help. I wonder if anybody knows reliable solution for this problem.
I have Ver.2012.3.41009 of VS, other than NuGet package I have the following installed packages: MS ASP.NET Web Tools, VS 2012 Color Theme Editor, VS Extensions for Windows Library for JavaScript
UPDATE: Full info about the exception (Not too much: inner exception is null, stack trace consists of single line):
System.NullReferenceException occurred
HResult=-2147467261
Message=Object reference not set to an instance of an object.
Source=Microsoft.VisualStudio.CodeAnalysis.Sdk.UI
StackTrace:
at Microsoft.VisualStudio.CodeAnalysis.SdkUiUtilities.GetService[S,T]
(IServiceProvider provider)
InnerException:
UPDATE 2: I've just found out this error is solution-dependant. On some solutions it persists while on others does not
Looks like a known issue of visual studio. SeeMicrosoft Connect issue for the status of the issue. As mentionned by others, disabling the NuGet package manager seems to be the only known workaround for the moment.
Nuget is a extension and "Properties access in a solution" should have nothing to do with Nuget theoretically. How do you access the properties in the soultion. Can you post some sample code ? Is it through the Automation model or VSSDK ?
Related
Just installed ODAC for Visual Studio 2017 version 19.3 from here: https://www.oracle.com/database/technologies/dotnet-odacmsi-vs2017-downloads.html to replace ODT for Visual Studio 2017 NuGet Package. Then I noticed my Oracle NuGet packages were gone in my VS solution, and I had to re-add them. But this time I used Oracle.ManagedDataAccess 19.3 (previously had used 12.2.1100), and Oracle.ManagedDataAccess.EntityFramework 19.3 (previously used 12.2.1100).
Now my EDMX gets an error when I try to open it: "Error 168: The provider did not return a ProviderManifest instance. The type initializer for 'OracleInternal.Common.ProviderConfig' threw an exception."
I found an interesting answer by Mitaka here: Entity Framework: The provider did not return a providermanifest instance, so I opened my EDMX with XML Text Editor and found my ProviderManifestToken="12.1". So just for grins, I tried "19.3" and "19.1" but neither worked.
Anybody know the magic value? I'm just hoping that is how to solve the error. Thanks.
Got it. "18.0"
It actually updated itself after I got a bunch of other kinks worked out including "There is a duplicate 'oracle.manageddataaccess.client' section defined." Turns out the definition for Oracle.ManagedDataAccess was in my WebAPI web.config and also the machine config. Had to update THIS specific machine.config:
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config\machine.config - do a search on "managed" and comment out in 3 places.
Then it let me create a connection in Visual Studio 2017 Server Explorer and open the EDMX. Finally the EDMX update wizard is no longer aborting on the Data Connection screen. Back in business.
I am using Visual Studio 2015 Enterprise to generate Coded UI Tests. Things have been working well until this morning. When I attempt to create a new Solution/Project, I am given the following error:
I am then able finish loading the project. However, I see another issue in solution explorer:
Note that there is no path given for the selected reference. If I try to remove it/add it back as a reference manually, I still do not see a path or version. I have tried the following:
Selected different .Net framework versions when creating the solution/project
Tried different project types: Window Forms, Class Library
Repaired visual studio
Repaired .Net Framework 4.6.1
So far I have been unable to make the error go away. Any other suggestions?
I was not able to resolve this issue. I ended up performing a reinstall of the OS/Visual Studio to get things working again.
Hi I have updated Manage NuGet package and my VS 2013 give "Object reference not set to an instance of an object" error Whenever I run program. I tried to find solution but failed. So I uninstalled VS and then reinstall. But the error is same even on making new project.
I had the same issue and was forced to revert to an earlier version of NuGet. v2.8.6 has imposed a dependency on .NET 4.5+ in a point release - bad behavior IMHO. See NuGet 2.8.6 causing dependency on .NET 4.5+?
I'm trying to create a SSIS project with a Script Task that uses Visual Basic Code.
In it, I'm trying to use the Microsoft Scripting Runtime COM object. My VS 2010 has installed the .NET 4.5 Framework but whenever I try to add the Reference it comes with this problem:
*Edit #2: Visual Studio actually pops up an error:
After checking the References Properties of the Project, the Path says: "The System cannot find the reference path". Even then you can manually reach it yourself.
Upon further investigation I found that ALL COM objects encounter the same issue:
I have seen a number of solutions pointing to a re-install of Visual Studio and the like. Which I have done with no success.
Does anyone have an idea of what could be causing the problem?
*Edit: I think it bears to point, i have tried some funny business with the Interop (setting it to true and to false does nothing). I saw some answers online but this made no difference.
(I'm running Windows7 and using Visual Studio 2010.)
I'm using ClamAV in a .NET Azure project, and I'm running into side-by-side errors whenever I run clamd.exe, either through my code or by running clamd.exe on it's own.
In Visual Studio 2010 I am getting the error:
Win32Exception was unhandled The application has failed to start
because its side-by-side configuration is incorrect. Please see the
application event log or use the command-line sxstrace.exe tool for
more detail
And in Event Viewer I get:
Activation context generation failed for
"C:\Users\pconerly\code\AntiVirus_source\WorkerRole\clamav\clamd.exe".
Dependent Assembly
Microsoft.VC80.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.6195"
could not be found. Please use sxstrace.exe for detailed diagnosis.
When I searched for "8.0.50727.6195" it led me to the 2005 redist, so I downloaded it
http://www.microsoft.com/download/en/details.aspx?id=3387
After a restart I am still getting the side-by-side error. Additionally, I think that the redist installer is not completing it's install-- like it's seeing visual studio 2010 and saying "oh, that's good enough, no need for me to install". I haven't tried uninstalling 2010 and using 2005, because the rest of my Dev team is using VS 2010.
What's the deal? How can this be fixed? I'm ready to pull out my hair.
The link Timores posted is the update for Visual Studio. The actual redistributable package is this:
http://www.microsoft.com/en-us/download/details.aspx?id=26347
The version you mention is actually at found here
Microsoft Visual Studio 2005 Service Pack 1 MFC Security Update
Timores is right: the redist should be this one, which is related to this KB entry
As you can see there, msvcr80.dll has been updated to version 8.0.50727.6195.
It is the "security update" of the "SP1" of the 2005 C++ runtime..
Your exe probably requires (through an internal manifest) that specific version.
If it is not found on the system (there's a lot of places searched for) nor in the current folder (with a suitable manifest aside) it won't load the exe since it is not able to "activate the context", that is load the specific DLL required in the manifest.
I had similar issues when my system got updated (windows updates) and the newly compiled EXEs were not working with an old-versioned runtime placed on the same folder.
I had to update msvcr80.dll and its manifest (which I found deep in \windows\winsxs) to make everything work.
Context activation is a tricky matter, anyway :)
HTH