I have a web application in VS 2003 (1.1) that i need to upgrade to Visual Studio 2010 and target to framework 4.0. But it showing the error like
"Internal MSBuild Error: Setting property without a project and without a pending global properties collection."
I had this problem, and the only thing wrong was that something in the folder was reaonly. Make everything writable and try again.
Related
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 attempting to upgrade our rather old TFS environment from TFS2008 to TFS2015. The upgrade of the server and database is not a problem and is fine.
The issue is our build machine. This is still a Windows 2003 Server that is running Visual Studio 2010 and VB6. We still have a need to use this build machine to build legacy VB6 projects. We have installed the TFS2010 XAML build controller on this server and successfully connected it to our test TFS2015 server. However when we try to run a Xaml build, (any Xaml build regardless of whether it builds VB6 or .NET) we get the following error message almost straight away.
TF900560: Could not start build: Cannot set unknown member 'Microsoft.TeamFoundation.Build.Workflow.Activities.TfsBuild.TargetsNotLogged'.
The XAML build are using the 'UpgradeTemplate.xaml' template and using the TFSBuild.proj we used under Visual Studio 2010.
We have a also set up a TFS2015 build controller on another (Server 2012) machine and that successfully starts the build process. However, our VB6 projects use a lot of third party components that will not install on Server 2012 so we can't use that.
Has anyone ever set up this kind of arrangement before? Is there anything we are missing or are doomed in this scenario? Obviously, we'd like to move away from VB6 apps, but that is not possible in the medium term.
When using Visual Studio Enterprise RC to create a new .NET Framework 4.6 ASP.NET Application using the Web Site template I am receiving an object reference not set to an instance of an object error. After dismissing the error the project seems to be ok, but I would like to be sure.
Both the Empty and Web API template work fine.
I have tried creating the project with Visual Studio in safe mode as well as creating a new project with a separate instance of Visual Studio attached for debugging. None of this has given me a clue as to what the problem might be.
Any idea what could be causing this issue? Or pointers on next steps to take?
You can now upgrade to the full Visual Studio RTM version. That should fix your problems.
I have a website made with vb and c#. I open the project in Visual Studio 2010 and there are no problems.
My problems start when I try to debug it. I have this error:
Could not load type 'projectName.Global
Also I need to convert it into a web application but when I do right-click on the project this option is not there.
I did all settings in IIS but I always have this error and I cant convert it
If it is not clear tell me, I will try to improve my question.
I am adding this custom build task to my TFS 2010 build workflow, however when attempting to add it (ColinsALMCorner.CustomBuildTasks.dll) to the toolbox, I get error:
'Could not load file or assembly file 'ColinsALMCorner.CustomBuildTasks.dll' or one of its dependencies. Operation is not supported'.
I have added all of its dependencies to (I admit, this is probably redundant):
1) the same location where the ColinsALMCorner.CustomBuildTasks.dll resides, which is ..\BuildProcessTemplates\CustomActivities
2) in the Public Assemblies folder: Microsoft Visual Studio 10.0\Common7\IDE\PublicAssemblies
And I have the build definition xaml file correctly importing the ColinsALMCorner.CustomBuildTasks namespace
Although the activity is set to target .Net 4.5, the documentation says that TFS 2010 / .Net 4.0 is supported, so I assume this should all be possible.
My Questions:
Is this possible with TFS 2010 / .Net 4.0 development environment? My concern is that the error message isn't telling the real story, for example maybe it is able to find it, however just not the right version of the assembly.
Is it likely that since the DLL targets .Net 4.5 I need to have all of its referenced dll's also be the 4.5 version? For example, it references Microsoft.TeamFoundation.VersionControl.Client however I only have the version 10.0.0.0 (which I assume the .Net 4.5 version of this might be 11.0.0.0)
Here was the solution, in short story format: I installed Visual Studio 2012. Result: I was able to add ColinsALMCorner.CustomBuildTasks to my workflow in Visual Studio 2010 without error. I assume this means there was a 2012 (v11.0.0.0) DLL or two required to use the activity in 2010, despite the fact that the requirements state:
Team Foundation Build 2010, 2012 or 2013