Is there a way to manage SSRS reports reports in TFS?
The SRSS and TFS servers are already installed and functioning. What I'm really looking for is to add a source control for "SRSS" in "TFS" so the report writers can use Visual Studio (2010) to checkout reports, make changes and check in. If source control is not possible, then what are my other options?
Any ideas?
You can export the report files and then put them in source control but as far as I know there is no way to get them into source control through visual studio (team explorer). You can add SSRS projects to source control from Visual Studio so if you move them into one of those you may find some luck. Out of the box there is no SSRS project.
Related
In my company, we are using Team Server Foundation 2010.
Last week when I was checking out some ssrs (sql server reporting services 2010) files, I obtained the correct files from TFS. I could see that the files were still connected to TFS.
However, I think there was a time last week where there was a message saying that I was working offline.
Now when I obtained the most current code from TFS, I do get the correct code. However I do not see that the code is connected to TFS any longer. Basically when using Source Control Explorer, I do not see that this code is linked to TFS
Thus I would like to know how to get my code back to accessed in TFS 2010?
Do you see the same problem with all files in TFS or only specific set of files?
Do you see this problem in only one workspace or in all workspaces on a single machine? Or does it affect all users?
What does it mean that files are not linked to TFS, can you post a screenshot?
TFS 2010 was quite weak story for offline and it worked only for solutions (as visible in Solution Explorer). Source Control Explorer always required connection to TFS
I'm also confuse about “files are not linked to TFS”you describle ,can you post a screenshot.
Simply offline mode means TFS 2010 goes offline (disconnect the connectivity properly between your local machine and TFS 2010 server) while your solution is already open though VS 2010.If you checkout files while you are in offline mode, then TFS 2010 source controls system doesn’t record or track any changes you made. But when you reconnect TFS server, the server will get you changes in pengding changes, then you can check in manually.
To get your solution back online to TFS you can try this solution:right-click on the solution name right at the top of the Solution Explorer and select the Go Online option.
More detail: How do I get my solution in Visual Studio back online in TFS?
You need to use the "go online" command to re-sync:
Cannot see go online option in tfs
Note: TFS 2010 is no longer supported and you should upgrade soonest
I got a project which includes both a windows service (a C# project/solution in VS2013) and some SQL scripts (a SQL Server Script project/solution in SSMS 2012).
Both of these use TFS as source control.
The strange thing is that pending changes differ between VS and SSMS.
In SSMS I only see changes to files in the SSMS solution.
In VS I see all changes in both solutions except new files added to the SSMS solution.
This means I can't check in all changes in one place and have them in one change set (unless I manually add the new SSMS files in the VS Source Control Explorer).
I am pretty new to TFS (coming from Mercurial/Git) so I still don't understand how many things work, e.g. how pending changes/source control explorer detect new files.
If you are using TFS 2012 or later, you can choose either a local or server workspace from within VS. There are pros and cons to each but with the local workspace you should be able to achieve this requirement. Visual Studio will detect new files that is within it's source control and add/edit/delete as a pending change as required.
What version of TFS are you using?
My issue is that I cannot add SourceSafe Database for source control within Visual Studio 2010.
Our team was initially using VSS for source control in Visual Studio 2010. During an evaluation of TFS, I switched my source control to TFS. It will be a few weeks before a decision is made on TFS, so I needed to switch my source control back to VSS. However I'm now unable to add a SourceSafe Database in Visual Studio.
Steps to Reproduce in Visual Studio 2010:
1) Access the 'Open SourceSafe Database' form via Tools->Options->Source Control->Plug-in Settings-->Advanced
or via File->Source Control
2) The list of available database is blank so I choose 'Browse'.
3) I browse to the srcsafe.ini file for my VSS database and select it.
4) I'm promted to confirm the Database Name - Click OK.
5) The database does not appear in the 'Open SourceSafe' Database form. The list of available databases is still blank.
Note that I can add the database fine outside of Visual Studio using VSS directly. However the databases I add via VSS do not appear in the Visual Studio forms.
I'm suspicious that this is related to "down-grading" from TFS to VSS which may not have been heavily tested at MS.
Any assistance is appreciated.
I installed VS2010, then i install VSS, then i have the same problem, cant connect to my VSS it by default opens (TFS)
the suggestion here, to reinstall, dont sound good, did a bit more searching and found this:-
http://social.msdn.microsoft.com/Forums/en/vssourcecontrol/thread/6c927805-bca6-445b-b406-0a0da8fa21d3
and found the easy solution that 'CletusLoomis' is looking for:
simply:-
hanks for your post.
Could you please try the following steps?
Open VS2010, then choose the menu: Tools->Options, then click "Souce Control"
click drop-down box under text"Current souce control plug-in", use "None", rather than "Microsoft Visual Source Safe"
thats it, problem solved!
:)
hope this helps someone else who found this page via google.
To do that you must run Visual Studio 2010 as Administrator. Just click on Icon using right button, Go to Properties, Compatibility, at the botton of screen you should mark Run this program as administrator.
That's all.
Must exist some file that the permission should be granted to all users, but instead of searching for the file, I preffer this solution.
Regards,
Luiz Ricci
My Visual Studio 2010 had very similar symptoms: having selected Visual SourceSafe 2005 in the Options I had the only menu option: Launch Microsoft SourceSafe
While following the steps provided by 'visual' (as of Nov 30 '10 at 8:00) I have found the following registry key, which needs to be switched to 0 to enable the SourceSafe menu options to be displayed in Visual Studio 2010. Once the registry key value has been changed to zero Visual Studio needs to be restarted and .. voila! Now I have an additional menu option Open from source control...
The registry key is as follows (for 32bit OS it would need to be slightly modified): HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\SourceSafe\Namespace Extension\DisableOpenFromSourceControl
Now, why it was disabled by default is beyond me.
Your installation of VS might be corrupted. I would recommend uninstalling VSS, VS, and TFS and then reinstalling VS and VSS. Unfortunately, this could take 4+ hours, but it should fix your issue.
I don't believe that my VS installation was corrupted. I do believe there is a bug in VS 2010 which does not allow me to use VSS for source control after having used TFS. Fortunately for me, our team decided to go forward with TFS for our project's source control. I never had to solve the problem. I believe that reinstalling Visual Studio alone would have been enough to solve the issue.
I had the same problem with Windows 7, Visual Studio 2010 and VSS. I noticed several things:
VSS as standalone program does always work on my system.
VSS works perfectly in my projects, if the UAC Level is the lowest, but not with the default UAC Level.
If I open a project file with VSS source control, Visual Studio tries to read the registry. It fails to read/write the keys in the registry with access denied. Therefore I changed the permissions in the registry of the SourceSafe keys to full access for all users. Now, VSS works perfectly on my system with default UAC security level.
I faced the same problem.
I am using Visual Studio 2010 and my projects added to Visual SourceSafe 6.0
The VSS database list was not prompted on my machine as well.
After a number of attempts for over 3 hours. Finally got a solution.
I run the VS2010 using Run As Administrator option. The VSS database list was visble.
I think the issue might be due to Access Rights of Registry in Windows 7.
What a nightmare this has been. Ultimately, you can set in domain or local policy.
Local Security Policy\Security Settings\Local Policies\Security Options\User Account Control: Run all administrators in Admin Approval Mode - Disabled
This means anyone in the administrator group does not have to have approval (The Dreaded Run as Administrator)to be an administrator. Can be set locally as above or domain wide. Solved a lot of problems for us.
Options -> Source Control -> Make sure the "Current Source Control Plugin" is correctly set.
Mine was set to Microsoft Visual Source Safe (Internet), and should have been Microsoft Visual Source Safe.
First, make sure you can view the database by visual source safe explorer.
Then, trying to proceed with these step...
Open Visual studio as Administrator.
Log in visual source safe by the database path. (it still disappears the database in "Available database" list.)
Is there a way to tell Visual Studio 2005 to just ignore source control binding when opening a solution? I sometimes need to load a solution for which I don't have access to the source control server, but Visual Studio insists on trying to connect anyway, meaning I have to click "temporarily work offline in disconnected mode" for every project in the solution (of which there are about 20) as it loads. For some reason, it also tries to check each project out immediately after I've told it to work offline, so I have to click past that dialog box too.
As I will never need to edit anything in this solution, is there any way I can open it and have Visual Studio just ignore the fact it has source control bindings in it?
Edit: Ideally, I'd like a way to do this without having to change the project/solution files. They change fairly frequently, so I'd have to redo any changes every time there was a new version (otherwise I'd just unbind them once and it wouldn't be a problem).
Thanks for the replies so far.
The source control bindings are stored in Visual Studio solution file (.sln). For TFS for example, it contains a global section for TFS information and the solution projects added to TFS. You can edit the solution file to remove these bindings manually. I would suggest making a copy of the solution file first. However, I would recommend removing bindins via Visual Studio. Open your solution and go through the offline scenario. Then go to File/Source Control/Change Source Control (VS 2008) to bring up the UI that shows you the source control bindings in your solution. There you can manage the bindings including unbinding them. Once unbound, the next time you open the solution, VS should not have a need to access the source control.
I've been looking for a way to disable Integration between SourceSafe 2005 and Visual Studio 2008. We are forced to use SourceSafe being in a corporate environment and all. SourceSafe is fine on its own if you treat it like a baby. As soon as you try to do anything approaching useful it starts to break. God forbid you try to use the integration with Visual Studio. Being that I didn't want the "Bindings removed" so that it doesn't confuse other devs on the team I needed to be able to tell Studio to ignore the solution and project bindings and continue on it's merry way.
I followed the registry hack suggested in the following post
Removing SourceSafe Integration from Visual Studio 6
Studio did what I wanted...sort of. It removed the SourceSafe integration. However when I opened up a source controlled solution it asked me if I wanted to remove the bindings.
"the projects will be treated as not under source control"
No I don't want you to remove the bindings from the files, I want you to IGNORE them. This dialog pops up every time you open the solution/project file and there is no way around it.
My solution at the moment seems to have worked...for now.
File->Source Control->Change Source Control...->Disconnect
I hope this helps anyone else in the position of having to use SourceSafe but can't remove the bindings from the files themselves. WHY, Microsoft, WHY would you put the bindings in the files themselves?
/rant
A question was asked recently about removing SourceSafe integration from Visual Studio 6. I need to do the same with Visual Studio 2008.
Our team uses Subversion and I have installed AnkhSVN, the Subversion plug-in for VS2008 (some other members of the team use VisualSVN). I find that SourceSafe "insists" on being the integrated source control tool of choice - the setting for source control plug-in in Tools > Options > Source Control seems to reset itself every time VS2008 is closed. This is very annoying and I want to get rid of SourceSafe.
I tried running the VS2008 install with the intention of switching off (effectively uninstalling) the SourceSafe plug-in, but there is no option for it.
Visual Studio stores source control preferences in the solution and project files. To switch providers, you have to first "unbind" the old provider.
Select File > Source Control > Change Source Control, select the solution and all the project files, and click "Unbind."
Save the solution.
Then you can change the provider with Tools > Options > Source Control.
Hand-editing the .sln and .proj files also works, but it's not exactly recommended.
Found it! MS's Help and Support site describes it, see section 2
Add a DWORD registry key at:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SourceSafe\HideInVisualStudio
Set it to 1. Restart VS2008 and the SourceSafe plug-in option is gone.
You can usually edit the *.sln file and *.??proj file with out an problems to remove these bindings. These two files are just text files so you can open them in Notepad, Wordpad, or Visual Studio.
Just remove stuff slowly and then save and try to load.
Not sure if this works, but you can try:
Tools/Options/Source Control: set Current Source Control plug-in to "None"
Open the solution - hopefully it will tell you the provider is missing and give you an option to remove the bindings.
There are several constraints/behaviors for my case:
1) The machine and the projects are shared by several developers and they should not be affected by my changes,
2) vs2008 automatically re-enables SourceSafe control (did not try the HideInVisualStudio registry solution because it's a global flag),
3) I can't remove the bindings in the projects nor un-install SourceSafe
So I have found a way which is not perfect but works good enough for me:
1) open regedit and go to this key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SourceSafe
there should be an entry
SCCServerPath
which should contain something like this:
C:\Program Files\Microsoft Visual SourceSafe\ssscc.dll
2) Modify the permissions for ssscc.dll in order to DENY the "Read and Execute" access for your userid.
Now, this is not perfect because you will have sometimes an error message message when you load a solution in VS2008 (There was a failure while initializing the Microsoft Visual SourceSafe source control provider. You cannot use this provider to perform source control operations.), but the goal is achieved:
1) No more source safe integration in VS2008,
2) Source Safe standalone is still working,
3) Other users are not affected by the modification.