Using Rational Team Concert (aka Jazz source control), when loading a new repository workspace to a sandbox I am encountering error CRRTC8550E, and the resulting sandbox is incomplete. I am using Windows 10, Visual Studio 19 and the RTC plug-in for Visual Studio (6.0.6.1).
The problem occurs when the repository contains symbolic links and RTC does not have sufficient permission to create the required links on the local Windows file system. The simple workaround for this is to run Visual Studio as administrator.
Related
I'ma bit stuck. Been using Visual Studio 2013 Community edition forever, to create and edit custom SCOM Management Packs in a local GIT Repository. I downloaded VS2019 (and 2017, just for luck), with a view to start using that, but it won't recognise any of my SCOM (MPPROJ) projects.
I figured I just need to update my version of "System Center Visual Studio Authoring Extensions v1.10.201.0" with the currently available download of "System Center Visual Studio Authoring Extensions v1.4.1.0", but this will not install, with the message "Another versin of this product is already installed. Installation of this version cannot continue. To configure or remove the existing version of this product, use Add/Remove Programs on the Control Panel"
Any attempt to so this, results in "The installed product does not match the installation source(s). Until a matching source is provided or the installed product and source are synchronized, this action cannot be performed" leaving me with a 'Browse' dialog box to find the original MSI"
Not sure what to do.
I currently have VS 2013, VS 2017 and VS 2019 all installed on the server, and both VS 2017 and 2019 will not recognise my SCOM Project files (labels them as 'Incompatible').
How can I continue working on my SCOM MPPROJ files in VS 2017 or 2019??
Ok, this was a few steps to fixing
Ran a repair in Control Panel>Programs & Features on the old VSAE install.
Successfully uninstalled VSAE
Reinstalled new 1.4.1.0 VSAE (x64) - Wierldy states it's v1.10.218.0 in Programs & Features
Existing SCOM Projects unable to open (new or existing) without error "Could not load file or assembly 'Microsoft.VisualStudio.TemplateWizardInterface..."
Opened VS Installer and used 'Modify' to install the 'Modelling SDK' component for VS 2019.
New error on SCOM projects:"Expected 1 exports with contract name....microsoft.systemcenter.authoring.presenter.ipresenterservice"
Opened VS Installer and ran a More>Repair on VS 2019.
Can now create a new SCOM Project, however existing SCOM projects have to be 'Reload'ed in the VS GUI to restore their SCOM MP file structure and remove the "Incompatible" status (Annoying when you have dozens of Projects).
Phew.
It's worth mentioning that before I ran these steps, I DID install MicrosoftProgram_Install_and_Uninstall.meta.diagcab and fed it the Uninstaller regkey GUID for the old VSAE that was installed. It didn't seem to fix anything, but did run a bunch of cleanup activities, so that MAY have also been a contributing factor to this resolution. Worth trying if the Repair doesn't work in first step.
Installed VS2017 RC - Started New Project ASP.NET Core Web Aplication(.Net CORE), selected Individual User Accounts as Authentication type. Try to run code generated with no changes and got the following error: Error occurred when trying to configure IIS Express for project... Error: ../.vs/config/applicationhost.config Error: cannot write configuration file
Looked at that file and it appears that it should have been writable.
FYI using VS2015 Update 3 everything builds and runs as expected including IIS Express.
I have encountered the same issue but deleting .vs folder worked for me.
I was having this issue, but only after the recent updated to Visual Studio 2017 RC (12/12/16).
I searched for a good hour and really didn't find anything, so I simply downloaded the latest IIS Express (v10) and it seems to have corrected the issues for 2017, but also for 2015 that started after the update as well.
IIS Express Download
EFS (Encryption File System) is known to cause file access problems. Ensure that EFS is turned off in your project directory.
More information:
https://blog.danielsmon.com/2017/04/03/cant-write-to-applicationhost-config/
I am using Team Foundation Server with VS 2010. I am facing a problem that when i am mapping a new folder to download the code from TFS, after download all the code, all files/folder in new folder get automatically read only attribute and i have to remove this attribute explicitly after it i am able to build the solution other wise it is giving me "Access denied" error. Is there any TFS setting which is making my project files as read only.
Not with TFS 2010, this is called "Local Workspaces" and is available from TFS 2012 onwards and works like Subversion.
What you are doing, by removing the Read Only flag, is fighting TFS. What you should do is perform a Checkout on the file before editing. If you are using Visual Studio to edit solutions/projects this will happen automatically providing you have your Solution and Project bindings setup. If you are editing files outside of Visual Studio, you can perform a checkout by:
Using Source Control Explorer in Visual Studio.
Using the Team Foundation Server Power Toys to install a Shell Extension into Windows so you can Right click.
Opening the file in Visual Studio and using it as a text editor.
Using the tf checkout command line.
By removing the read only flag, you are allowing yourself to edit the file, but not instructing TFS that you have changed it, so TFS won't know to check it in when the time comes. TFS doesn't scan you workspace for changes like Subversion.
Here is what we are trying to do:
In a TFS collection we set up a TFS project “BuildBusinessWebsite”. For this project we will have .Net solutions, SQL Server Reporting Services (SSRS) reports, and SQL Server Integration Services (SSIS) packages. (I have to do development on all three.) We have chosen to set up a folder structure like this in Source Control Explorer with solutions and code in each directory folder:
BuildBusinessWebsite
Development
Application
SSRS
SSIS
Test
Application
SSRS
SSIS
Production
Application
SSRS
SSIS
Now, we are currently developing the SSRS reports and the SSIS packages using Visual Studio 2008 and the application is being developed in Visual Studio 2010. When you connect the second Visual Studio 2010 environment to the same working directory (Local Path: Not mapped) you get the error “The path … is already mapped in workspace …” issue because it is already mapped to the Visual Studio 2008 directory. I need both environments mapped to the same directory as I do not want to keep multiple directories on my machine up to date with “Get Latest”. I am also currently testing the migration to Visual Studio 2012 where it is also asking me to map another location for TFS. My current work around is to create another layer of folder mappings as C:\TFS2008, C:\TFS2010, and C:\TFS2012 with the folder structure above in each. Is there a way to consolidate all these for one location for all the code?
Second issue related to the above is with branching and merging: If there is some way to fix the above then this one is moot, however, when pulling down the folders above from source control and you are utilizing branching and merging, the branching and merging connections between prod, test, and dev do not seem to pull from TFS. They seem to be local to my workspace and machine. Considering the example above where I branch my application from Production to test and test to Development in Visual Studio 2010, when I use Visual Studio 2012, map the Source Control Explorer to another location on my hard drive, and “Get Latest”… After it comes down I lose my branching and merging having to set them back up. Is there a better way to set this up?
Thank you all ahead of time for reading this and thoughts you might have would be greatly appreciated.
TFS Workspaces are uniquely identified by:
Workspace Name
Workspace Owner (AD Account name)
Computer Name (The Computer which it is on)
Team Project Collection it is in
The workspace mapping should have nothing to do with the "environment" you are working in. You should either use the TF Admin command to create your workspaces or go to File->Source Control->Advanced->Workspaces... in Visual Studio. Also, create only 1 workspace and do it at the root folder.
Project was working on PC number 1. Copied project to external drive and trying to load project from PC number 2. Both PCs have similar install of VS2010 premium. Can run the website ok locally. VS2010 is giving the following error when opening the project.
visual studio 2010 cannot be opened because its project type () is not supported by this version of the application
Error indicates something isn't installed on PC number 2. But how can I find out what software is missing?
The Visual Web Developer check box was not checked as part of custom Visual Studio install. Doing an change/repair and ticking that box fixed the issue. Strange - other web projects loaded fine. This is the only project that errored.
On the computer where this works, goto:
Tools > Extensions
This should give you a list of the extensions you have installed and you can cross reference it against the computer where it doesn't work.
I'm guessing you have an MVC project and haven't installed ASP.NET MVC on the second machine.