Quite new to SSIS. To open existing SSIS packages in Visual Studio and I clicked SSIS but it has opened Visual-Studio and not my packages.
In solution explorer showing that SSIS packages(incompatible) and below that "the application not installed",but actually in Extensions windows its showing that installed SSIS. Please help me out resolve the below error (Image).
I tried to modify the package and uninstalled the SSIS tool and installed again. But still same problem
I had the same problem and I found this menue choice in Visual Studio. I right clicked the Solution, chose Resolve Errors and it resolved my problem.
I think you need to install SQL Server Data Tools for you to launch the project and test in your local SQL instance. If you're, like me, fairly new to SSIS package, I suggest you follow this Microsoft official tutorial so that you are familiar with ins and outs of SSIS package.
If you are sure that you have installed all necessary components, please ensure that VS > Tools > Extensions and Updates > Microsoft Integration Services Projects is enabled. Once enabled, restart Visual Studio. It might still look the same. Last step is to right-click on the project and choose "Reload Project".
I always ignore and shut down the carking update notification when opening SSIS, until I encountered this error.
I tried googling it and tried "reload project" and "Resolve errors" option, I also uninstalled SSDT and reinstall it, I also disabled and enabled SSIS in "Extensions and Updates" Bar. They all failed.
So I updated SSIS since I'm bored and tired, then I tried "reload project" and "Resolve errors" option again, the magic is everything going fine, like before! It's just my experience, not representative.
I already faced the same problem, for some reasons the SSIS extension was disabled.
So to resolve this issue you need to go to :
Extensions > Manage Extensions > Installed
Make sure that the SSIS extension is enabled then close and reopen you project.
Related
My Visual Studio does not highlight or autocomplete any Unity3D commands any more. I created a new script when noticing that. I restarted VS, reinstalled VS, also reverted all script changes I made today in my project but the result is still the same. Also I now get errors when trying to open my project file. It says it needs a migration and isn't compatible with the current Visual Studio version installed.
The actual error reads "The application that is based on this project type was not found." [translated from German].
I found similar posts on the web where reinstalling VS resolved the issue. Unfortunately, it did not for me. This is how it looks:
Anybody knows how I can fix this?
Ok, I was able to resolve this issue using this trick:
"Do me a favor... if this is Visual Studio 2017... hit your start menu and find Visual Studio Installer... Run it... select "Modify" and select individual components... find Visual Studio Tools for Unity... if it's installed, untick it and uninstall it, then run the installer again and reinstall it. Otherwise, just tick it and install it."
The Autodesk ObjectARX project wizards fail to create projects in visual studio professional. I only see in the status bar at the bottom that it has failed. How can I tell what's wrong?
I've checked the visual studio logs (using devenv.exe /log) with nothing reported. And I don't see any other logs. What else can I do?
I should add that there should be a ui, but nothing appears. It fails right away.
Uninstall the wizard.
Right click on wizard setup file
Troubleshoot compatibility and follow steps to install
Try, it works
You should put the ObjectARX folders (inc, lib or so) to "C:\ObjectARX".
Another place is unacceptable.
I had the same problem because on wizard 2018 installation leave field "Registered Developer Symbol" empty. Then on using wizard you can change this symbol to any other.
Other name for ObjectARX directory allow successfully install wizard 2018 but then will be problem in project settings where this path hardcoded as c:\ObjectARX. So better use c:\ObjectARX.
I'm running Visual Studio 2012, when I add a new File/Reference to a project the message box appears showing the error message
set property 'system.windows.resourcedictionary.deferrablecontent' threw an exception
I read an MSDN article suggesting to run the command devenv /resetuserdata on visual studio command prompt to resolve this problem, tried it but didn't work for me. In fact the command prompt shows the Unknown Error message.
Some addins cause this issue for me so have had to workaround it whenever it occurs:
In Vis studio -
Tools > Options > Environment > Add-in Security, uncheck 'Allow Add-in components to load', OK
Restart vis studio
The error shouldn't occur anymore, so go back to
Tools > Options > Environment > Add-in Security and re-check Allow Add-in components to load, OK
To be specific, I get this error when trying to add files to projects and manage Nuget Packages.
Update
I now make a point of opening
'Tools > Nuget package manager > Manage nuget packages for solution'
whenever I open up a new instance of Vis studio, before loading a solution, just to make sure the window loads properly
That way I know I won't get this issue.
In my case it was a style with the same key defined twice in a ResourceDictionary (WPF)
I have Windows azure tools for Microsoft VisulStudio 2013- v2.2 and Windows azure tools for Microsoft lightswitch VisulStudio 2013- v2.2.
I uninstall only Windows azure tools for microsoft lightswitch vs 2013 .
It's working fine...
I fixed it. The resolution was to remove the Windows Azure Tools for Visual Studio 2012 which I was not actually using, and the error went straight away.
In my case it was to first launch Visual Studio in safe mode. You can create a shortcut for visual studio with a target like this:
'"F:\Program Files\Visual Studio\VS2013\Common7\IDE\devenv.exe" -safemode'
Once launched in safe mode, you can remove the problematic extension via the Addin Manager. However, this wont work for some extensions, as the uninstall option might be disabled for certain extensions when running in safe mode, particularly if you have already uninstalled another extension in the same session.
In My case the problem was caused by Paradox Game engine, in which I had uninstalled it via 'Programs and Features' - which in return did not remove the extension which was originally installed via Nuget package. Uninstalling Paradox via "Programs And Features" left the extension itself still registered in Visual Studio, presumably causing a hidden NullReferenceException.
This issue can be caused by any extension that may have an error in it, or by extensions that were not properly uninstalled.
Also, see this article...
The mentioned issue can be resolved by simply restart the Visual Studio. :P
Also seem to be able to get around this by closing the project and vis studio instance, re-opening, then when the start page/open project screen appears selecting Tools > Extensions and Updates..., then pressing Close
Now open the project and the error doesn't get thrown when trying add files or manage nuget packages, weird.
Just annoying you have to remember to open Extensions and Updates each time...
Other wise make sure given Resourcedictionary.xaml path is correct or not
I had to remove Xamarin from Add/Remove Programs in Control panel and restart Visual studio to fix this.
I had this problem with My Devexpress Project in VS 2015
What finally worked for me was.
Close my solution,
Close Visual Studio,
Open Visual Studio,
Create a New dummy project,
Add a form to it,
Close and save the new project,
Reopen original project and all was ok.
for everyone else who are working in silverlight sdk environment with windows phone8 sdk.
The versions of sliverlight which are compatible with visual studio versions -
vs2012- sliverlight sdk 4
vs2013- silverlight sdk 5
I was integrating in vs2013 and as soon as I updated it with silverlight sdk 5, The errors went away.
In my case it was the Line Endings: you can have different formatting and by copy pasting some code one file got a different Line Ending. It was enough to File > Save As and then click the little arrow next to the save button.
Then click on save with encoding and choose the one you are using in all other files.
See Andrew Truckle's answer.
I hope this helps
Visual Studio 2012 will not allow me to set multiple startup projects.
I have tried:
Right-click the solution / Set StartUp Projects...
Result: Nothing happens.
View / Property Pages
Result: Popup "Object reference not set to an instance of an object."
I have no add-ins running, and disabled all extensions that can be disabled without uninstalling. Active extensions are
Microsoft Web Developer Tools
NuGet Package Manager
Visual Studio Extensions for Windows Library for JavaScript (1.0.8377.0 AND 1.0.9200.20512
VisualSVN
Is this a known issue? Is there a fix/work-around? Can I specify the startup projects by editing the .sln/.csproj file if the VS2012 UI continues to fail?
I'm pretty sure this has to do with NuGet Package Manager. I did as described here.
Uninstalled NuGet Package Manager in Tools => Extensions and Updates... and restarted Visual Studio 2012/Visual Studio 2013 Preview. Now I can happily configure my solution properties again!
Installed NuGet Package Manager again and the problem reappeared. :(
This is a palliative answer. If there's a definitive answer, please share it! :)
Make sure you vote on this Connect Bug.
Found this post while searching for a related issue I was having. I thought it would be helpful for others to know what I found.
My problem was trying to switch between start up projects, IIS Express would always load the same project. My solution was to edit the project properties >Web> assign a different port number for each project. Now when I select Set as StartUp Project... it actually works
Note** I did not have any issues with NuGet probably because I'm using the released version of 2013
When i try to access my solution Properties, i get the following error:
Object reference not set to an instance of an object
I am using VS 2012. What could be the cause of this?
Some extensions may cause this.
Try disabling extensions and restarting Visual Studio.
Quite often error will be gone even if you re-enable extensions after this.
There's a bug report on Microsoft Connect (link).
It is marked there as "Closed as External", but it seems that it may occur randomly with any extension, so would be worth voting it there to bring it to Microsofts attention.
In my case, the problem was solution-specific. NuGet was causing this error, but not the extension itself but a NuGet package that generated an error on VS load. When I opened NuGet Package Manager Console I saw a big red text with a description of the error. In my case it was T4Scaffolding.Core package, which in turn is a dependency of MVCMailer.
If this is your case, you will probably see what package generates an error in PM Console.
I faced this dialog too and i'm not sure what exactly causes this as i couldn't even open the NuGet console to see detailed error messages.
Closing Visual Studio, deleting %AppData%\Microsoft\VisualStudio and restarting Visual Studio worked for me as it causes a reset of various things like window configurations.
I think if this dialog is displayed some files may be corrupt in %AppData%\Microsoft\VisualStudio and by deleting that folder Visual Studio can start normally again.
Update:
The issue arises on my machine when i start Visual Studio by using "run as administator" whereas Visual Studio has been started before without that option and %AppData%\Microsoft\VisualStudio had been created without the administator association.
Visual Studio 2013: I had this issue when I tried opening TOOLS -> Extensions and Updates.
I used #ViRuSTriNiTy idea, but only cleaned the files from:
C:\Users[myUserName]\AppData\Local\Microsoft\VisualStudio\12.0\Extensions
There are 2 cache files over there.
Deleted them and restarted VS2013 and it was fixed
The way it was happening for me might be unique to me/my setup, but I'd love to know if anyone else has this happen, and if they find out why:
If I launch an .sln file by double-clicking it, it will load VS and I can right-click the Solution and get Properties to come up no problem.
If I go to "Open Project" on the Visual Studio welcome page or from File > Open > Project/Solution, navigate to the .sln file and launch it by selecting it and clicking "Open" in the File dialog, that's when I have this issue.
I'm going to just always launch the .sln file from now on, but I'd love to know why this happens when using "Open Project" from the welcome page or from File > Open > Project/Solution! I tried going into Tools > NuGet Package Manager > General and I unchecked the options for allowing NuGet to download missing packages and Skip applying binding redirects, and under Package Sources I de-selected the checkboxes (my dev machine does not connect to the internet). Environment > Extensions and Updates: I tried it with and without "Load per user extensions when running as administrator" and running it as an Admin and without running as Admin. Also tried just deleting everything at C:\Users\me\AppData\Local\Microsoft\VisualStudio. No change from those 2 bullets above.