I am using Visual Studio Express (v4.0.30319) singing to the tune of Visual Basic, and I'm using Source-Gear for my source control Visual Studio integration.
When I open a project I have to do it via the source control menu, and when it opens I get a warning message: "Unable to read the project file 'RemotingClasses.vbproj'."
After clicking the okay button, everything seems to work fine with the padlocks and checking out files, but I really don't like that I can't open a project from the splash screen, and that error box looks really bad in front of clients, who are inclined to panic at the very sight of the "E" word (error, that is)
...Fatal or not ^_^
Can I get rid of it?
Source Gear is not compatible with Visual Studio Express
Related
Using Visual Studio 2019, VB Windows Forms App(.Net Framework) template, my students are building projects using multiple forms, pictures (as background images and in picture boxes) and timers. When they have two or more pictures, the programs crash irretrievably.
The error message is:
Error while trying run project: (path to project location) Access is
denied.
Even if they remove the pictures, the error remains and the program no longer works. I never experienced this problem when we were using VB2015.
My student assistant tried to replicate the problem on (Vis Studio 2019) his home computer and couldn't.
If you're using an antivirus you may add an Exception to the project path.
You may also try to run VB2019 as Administrator to see if that was the problem, click on the VS2019 icon using the right button of the mouse and then click on Execute as Administrator.
I recently used the repair function in my Visual Studio Installer that I thought could fix the error message: Microsoft data transformation services designer package did not load correctly. However it turns out there is a new error message when I wanted to load my previous project: The "Package" package did not load correctly.
If I continue the loading, I will receive some other warning message in the solution Explorer saying my project is "incompatible" and "the application is not installed":
I initially also tried to follow some online solution and tried to repair Microsoft SQL Server Data Tools in control panel. It doesn't allow me to repair and says Setup Failed almost immediately after I click on the repair button.
Initially I was trying to add an WCF extenion in Visual Studio but seemed failed and threw the first error message to me. Then when I try to repair, the first error message is gone and I was given the second error message. Now I stuck in there.
I have also checked if SSDT is included in the installer and New project types:
It seems the SSDT is selected in the Visual Studio Installer and all my current project types are listed in the screenshot as well (previously I was able to see Integration services as well but now after the repair I can't).
I'm using Visual Studio Enterprise 2017 on a test server that a few people have access to (I've also tried to restart the Visual Studio and the server but it didn't help).
Hope I can get some suggestions here, really appreciated.
We are using Microsoft Visual Studio 2008 for a VB.NET solution on a Windows Mobile 6.5.3 Professional Device.
The solution compiles and runs on the device.
However, should we select
Debug > Start Debugging
while in Visual Studio 2008 the deployment starts and then stops enunciating the error
"The system cannot find the file specified"
and a dialog box stating
"There were deployment errors. Continue?"
Clicking "Yes" on the dialog box displays
Unable to start program '%CSIDL_STARTUP%\Program Files\Solution\Solution.exe'.
The data necessary to complete this operation is not yet available.
We have reset all settings under Tools> Import and Export Settings without success.
I'm trying to publish a DB project in Visual Studio 2013 Professional and the "Publish" button do nothing.
In project properties I checked "Create script (.sql file)". I right click the project name in solution explorer > Publish... > Load Profile (a profile that works for my colleagues) > Publish
Nothing Happens, not an error, warning or anything (same with "Generate Scripts" button).
Visual studio error logs say nothing and I tried to restart the PC, Visual studio and SQL server.
Thank you!
If you have an Azure Cloud Explorer window open in Visual Studio (could be table, blob or queue), that leads to the Publish of an SSDT project hanging.
Close the window and start a new Publish operation. It may take a little longer than usual but eventually that will progress and you'll be able to close Visual Studio as normal.
Thanks to Noel Abrahams for his comment that led to this answer.
EDIT: putting it here as an answer so that it can be more easily found but credit goes to Noel.
Found a fix on the MS Connect site.
In my publish profile I had set the connection string as so:
<TargetConnectionString>Data Source=.\sql2008r2;Integrated Security=SSPI;</TargetConnectionString>
According to the comments on Connect, it doesn't like Integrated Security=SSPI. Instead you should use Integrated Security=True;:
<TargetConnectionString>Data Source=.\sql2008r2;Integrated Security=True;</TargetConnectionString>
Then it all works fine.
I cloned the solution from VCS to a new directory and only this helped.
Other symptoms that I had with this issue:
While editing a table .sql script, Design pane didn't work.
Integrated Security=True; was set in my publishing profile. So Rhumborl's answer is not about my case.
If the solution folder is copied to another machine the issue is reproduced there too.
I tried to Clean Solution before re-cloning, but it didn't work.
For me publishing the database project to a new sql server database with a different name allowed the publish to proceed. Once I'd done that I was then able to publish to the original database again.
I found that having an Azure Queue or Blob Storage opened in Visual Studio Professional 2015 meant that clicking Publish did nothing and I couldn't close the application. After closing those windows which I had launched from the Cloud Explorer, I had to click Publish once again to kick it off. A strange bug.
I just installed Visual Studio 2012 Ultimate and I am trying to create a managed code extension project for Excel 2010 (32 bit Office Professional Plus). I have tried using the .NET 4.0 template contained in VS Ultimate for an Excel 2010 workbook. When I create the project everything looks fine until I run it.
Excel opens and I get the error message "The customization assembly could not be found or could not be loaded. You can still edit and save the document. Contact your administrator or the author of this document for further assistance." The details section is blank.
I have tried everything I could think of to figure this out and I have run out of ideas. I removed all addins from Excel except for the VSTO Design-Time Adaptor for Excel. I removed all personal macros. I set every directory I could think of to "trusted" in Excel and lowered the security settings for all options to "enabled (not recommended)". I completely uninstalled Visual Studio and re-installed. There are no errors or warnings showing up in Visual Studio. I also checked to make sure ".NET Programmability Support" was installed for my copy of Microsoft Excel.
I would link my code but I haven't written anything. I can't even get the default template to load when I run the project. A few others at work have the same setup as me and VSTO runs fine for them using the same steps. I even had someone send me a working project but it gives me the same message when I try to run it.
Is there anything else I can check to see where the problem is occurring? I tried setting break points in the project but it is failing before it gets to any of them.
Thanks so much for your help.
I've run into the same problem with Visual Studio 2010.
I isolated the problem to an SSRS reporting link we were trying to run from the add-in. I removed all the reporting stuff (service reference, sub-dirs, etc.) - the add-in runs fine.
We just ran into this and discovered that a method had a system exception that was not handled. It was hard to track down but once the culprit method had an exception handler the customization finished loading properly.