I have recently issued a Changeset Comment Policy in my team projects, following the steps at https://stackoverflow.com/a/13981350/2713582.
Thing is, even when someone supplies a comment on the changeset, it still shows up a policy override window, stating that the field is blank. Oddly enough, It does not happen in my machine.
We're using VSOnline, alongside with VS2010 and Windows (8.1 / 10).
Did anyone ever face this issue?
If you are using VS2010 and can't check in the code.You have missed the last paragraph with the above tutorials page.
Note: In Visual Studio 2010, you will have to install the Team Foundation Power Tools on all client machines - those without it installed will not be able to check in code.
Related
I have recently installed Microsoft Visual Studio 2015 Community Edition on my laptop.
Since the time of installation I have been facing a few issues.
I was not able to even access the New Project option itself.
Some of the times I will be able to access it however, sometimes it does not even allow me to access a single file of my solution in the startup itself it gives me an error.
I have attached a set of five screenshots in this query. There is some blank space after users path, I removed an extra folder name(username) from the path so dont get confused with that.
The detail of all the screenshots are as follows:
1) This is the image I get when I launch the Visual Studio on my laptop.
2) Once I click 'NO' option on the first dialog box I get a new one stating an error with the source code.
3) Once that is done, I move onto Solution Explorer to access the solution and I get this log.
4) When I try to access the tools tab to check for options I get this error message.
5) I had even tried to create a new project and the following error provided in this screenshot would appear.
I am not able to understand where I could have gone wrong or what happened that has corrupted the application to this extent. Is it an installation issue or are there some bugs in this version of Visual Studio, if there are any I would be more than happy to move to previous versions as I was a lot happier with them than this one.
If someone would help on this concern I would be really thankful.
Regards,
Harrisson
First, I went ahead and uninstalled the current version of Microsoft Visual Studio 2015 from my system. Then, I searched and removed the data from the temporary files related to MS VS 2015 from the following paths:
C:\Users\Username\AppData\Local\Microsoft\VisualStudio
C:\Users\Username\AppData\Roaming\Microsoft\VisualStudio
Once this had been done, I went ahead and installed Visual Studio 2015. After installation, I installed the additional support directories for Visual C++. You can do the same for the platform you wish to work on.
Then I installed updates from the following link:
https://www.visualstudio.com/en-us/news/releasenotes/vs2015-update3-vs
Once I started the solution it worked perfectly fine after that with no errors.
I've got trouble with my copy of Microsoft Visual Basic 2010 Express.
I installed it about a year ago. Since then I've used it several times without any problems. Now, I haven't used it for some weeks and now, when I try to start the application, it crashes after the welcome-screen with a not-helpful message. Because I use the german version of Visual Studio, I don't know exactly, how this message would look like in english:
German: Ein Aufrufziel hat einen Ausnahmefehler verursacht.
English (freely translated): A called target has caused an exception.
So, as you see, this Error Screen does not give many information. It is also not possible to gather more information. After clicking OK to the error, the application simply shuts down.
Some details
I am using the german installation of MS Visual Basic 2010 Express
I've got also installed the german version of MS Visual C++ 2010 Express (does not work as well)
Both applications does not work with user permissions nor with administrator permissions
No possible Compatibility-Option (Compatibility Mode, Reduced Color Mode, etc) fix the problem
I work inside a physical Windows 8.1 machine
I installed all updates, that came with the automated update feature of windows
I've got another copy of MS Studio Express inside a VM (Windows 7), working properly
I do not remember exactly what I have changed since my last use of VS, I think I installed Far Cry 4 AFTER my last use, wich came with some .NET components. But I don't think there were other big changes inside the system.
Because the error message is so inconcrete, I do not know, wich further information can be useful, nor I can imagine any problem, that suddenly occured. So I hope somebody got a similar problem and knows how to fix it.
The best option is to go for visual studio community 2013.It's free and you can recover your previous work.
You can download it here.
[http://go.microsoft.com/fwlink/?LinkId=517284][1]
Even if you find an error go to build->clean solution.It will work like wonder.
thanks
N S Deo
I am using Visual Studio 2013 together with TFS 2012 since a few weeks. Until yesterday I always had the Comments Textbox in the "Pending Changes Window". Now it has dissapeared and I can not find a way to get it back. This is a serious problem since it is mandatory to give comments to every checkin.
Can anybody tell me how to get the comments textbox back.
Can you post a screenshot of your Pending Changes window? It should be right here:
I recently had to struggle through this issue myself and found there is very little information out there on how to resolve it.
For my situation, what finally fixed the issue was removing the 2012 version of TFS Power Tools and upgrading to the 2013 version. There are several members of my team who are using the combination of TFS Power Tools 2012 and VS 2013 with no issues, I'm the only one who saw this.
I suspect that this was not a power tools issue as much as it was a problem with VS caching some TFS data locally. I tried a number of options to clear caches in both VS and TFS and nothing worked until I did this uninstall/reinstall.
Regardless, after the TFS power tools upgrade and a reboot, the Comment box was back. Hope that helps!
EDIT: I should also point out that not only was my "Comments" section missing, I also had no "Policy Warnings" section which we require on certain projects of our TFS.
I had exactly the same issue right after installing NCrunch 2.4.
Uninstalling it brought my comment box back.
Having the same issue. Vanished today. Have not installed anything for weeks. I had 3 Visual Studio 2013 up at the same time. 2 was bugged, 1 was not. I closed the 2 buggy ones, and then the working one hoping that last one would save its settings last. Did not work. Now I have no way of adding comments. I can check in anything without the policy blocking me like it normally does when I do not enter a comment.
UPDATE: A simple reboot of the client solved it. The Comment is back!
Just installed VS2010 express for Windows Phone last night. Install went smoothly. It creates a project, compiles, and deploys the app to the emulator.
Here's the problem: When I try to "Add Reference" through the Project menu, I do not get the Add Reference dialog box. Same thing if I right click References in the solution explorer and click Add Reference. That's not all. "File...Open" and "File...Open Project" also fail to throw up an open file dialog box. When attempting any of these actions, the IDE quickly loses and regains focus. Even pressing a keyboard shortcut (Ctrl+O) causes the IDE to quickly lose and regain focus, but no open file dialog box appears.
This is what I have tried, not particularly in this order:
1. Turned off UAC
2. Monitored file and registry access using Process Monitor during a File...Open operation. File activity showed mostly "SUCCESS" with a few "FAST IO DISALLOWED" and a few "INVALID DEVICE REQUEST" results. Registry activity showed mostly "SUCCESS" with some "NAME NOT FOUND" and a few "BUFFER OVERFLOW" results.
3. Created a new, clean Windows account to run the IDE from
4. Forced a test project to add a reference to "System.Xml.Linq" by editing the ".csproj" project file. Project failed to load in the IDE.
I don't have these problems at all on 2 other Windows 7 computers with VS2010 C# express beta 2 installed. One machine is 32bit and the other 64bit, both Home Premium edition.
My system: Windows 7 Home Premium, 64bit
Other Visual Studio products installed: VS2008 C# express, VS2008 C++ express
One other thing to note: Several months ago I installed the non-phone distribution of VS2010 C# express beta 2, and I had the same exact problems. Back then I chalked it up to being beta and went back to VS2008 C# express, where I do not have these issues.
Matt, if you're still reading this post, I have a solution:
Do you have the Tablet PC Input Service disabled? Enable and start it. This was suggested to me over on the MSDN forums, and it worked for me immediately. I have this service disabled, but I turned it on, fired up VS2010, and it just worked right off. I confirmed this solution by turning the service off again, starting VS2010, and noting that it breaks once again. Turned the service on once more, started VS2010, and it works perfectly. Amazing.
I do not think it's acceptable to require this particular service just for VS2010 to function correctly. Hopefully they fix this in the inevitable service pack. FYI, I had this service disabled because I turn off all services I don't require. So now I have two "wisptis.exe" tasks eating up ~8MB of RAM and starting every time I turn on the PC. Or I can shut the service off again and just resort to my previous workaround. haha
Here is a work around.
Just run wisptis.exe from command line and start the visual studio.
If you don't wanna run each and every time you restarts the computer,then just put wisptis.exe in a .bat file and move it to the startup folder,so that it will be automatically executed on each and every startup.
EDIT 1 :- Or else just press 'WIN'+'R' and type 'wisptis' and press 'Enter'.
I experienced the exact same problem. I'm running VS2010 Express on Windows 7 (x64). Re-enabling the "Tablet Input" service "fixed" the problem.
VS2010 has always worked fine, and then suddenly for no apparent reason "ctrl-O", "Add Reference", "Open Project", and other similar functions stop working.
No amount of repair/uninstall/reinstall would fix the problem.
I always disable the "Tablet Input" service on Win 7, because I use a Wacom tablet, and dislike the visual notification of (tablet) mouse clicks this service causes. VS2010 has so far been working fine in this setup with Tablet input service disabled, but then suddenly the problem arose, and I had to re-enable the "Tablet Input" service to make it go away.
I have another computer with the exact same setup - Win 7 (x64), VS2010 Express, Wacom table, and disabled "Tablet Input" service - and here VS2010 is still working just fine. Both computers also have almost identical software installed and updates installed, so I still have no idea where the difference lies.
Has anyone had more luck in finding the root cause?
I also use Power Toys, but I have not been able to correlate this installation with the problematic behavior of VS2010.
I'm having close to the same issue with the exception that my New | Project dialog works, but Add Reference and Ctrl + O just cause the interface to lose focus and regain focus without every launching the dialog. I have tried running devenv /ResetAddin and devenv /ResetSkipPkgs, but neither helped. I have UAC turned off as well. I don't experience the issue with VS2008.
Here's my setup:
Windows 7 Ultimate x64
Visual Studio 2010 Ultimate RTM
Visual Studio 2008 Team System Developer Edition with Team Explorer 2008 and VS2008 SP1
The only addins I run:
GhostDoc
.NET Reflector
Other Related Products I run:
Microsoft Expression Studio 3
SQL Server 2008 Developer Edition with SP1
tonight I uninstalled the VS2010 Express beta 2+phone tools and installed the now final RTM VS2010 Express C#. It STILL had the problem! For kicks, I tried importing a VS2008 project because it has some extra references in the project, and I was curious how they would be handled. The project imported successfully, but compiled with errors that it couldn't find a reference for a SyndicationFeed object, even though the reference for it was successfully added to the References list upon import. I remove the reference (System.ServiceModel.Web), hold my breath, and try to Add Reference one more time. Amazingly, the Add Reference dialog pops up, I add the reference back, recompile and bingo. File...Open and File...Open Project now throw up the proper file open dialogs as well.
To be sure this isn't a fluke only related to importing an old project, I shut down VS2010, start it back up, create a brand new project and try Add Reference. It works still. The File/Project dialogs also show up. I have no idea how, but importing a VS2008 project apparently made VS2010 correct itself on my machine.
Thank you for replying to my post. After hours of Googling over the past few days, your post is the first I've seen of anyone else having this issue besides me.
I found a workaround, but it's annoying having to do this:
1. Create a new project
2. Close VS2010, don't bother saving the new project
3. Start VS2010 again, and everything works as it should. I can access the Add Reference dialog, and I can do a File...Open and Open Project from the menu and toolbar.
If I close VS2010 and start it again, it is broken once more. Performing my workaround fixes it again for that session.
Still looking for a permanent solution.
I finally figured out a work-around. If I temporarily disable the Power Tools, the original Add References dialog opens fine. After adding my references, I can enable the Power Tools again.
I've recently put Windows 7 on my development PC, and I have Visual Studio 2008 Team System Development Edition, and SQL Server Management Studio 2008, and for some reason I can't seem to step in to any SQL code for debugging in SSMS.
Before I formatted in favour of Windows 7, I was able to debug on the same two SQL servers I'm trying now with the same software, so I'm guessing it's something to do with client configurations. Regardless, I tried all the steps I could find to enable SQL remote debugging but nothing has worked.
When I attempt to debug or step into the active query window, the debugger simply runs the code without stopping at the start or any breakpoints.
If I try use Visual Studio (running as Administrator) I get the following error:
T-SQL execution ended without
debugging. You may not have sufficient
permissions to debug.
Anyone got a clue what to do here?
EDIT
I'm still having this problem. I re-installed the latest SQL Server Management Studio from MSDN's latest SQL Server 2008 download available, and patched it with SP1, but this same problem still happens. Other people in my office are able to debug code with the same version client, and same permissions (set using group permissions) so I'm at a loss as to what is causing this.
FINAL EDIT
Solved! The issue was simply a domain authentication issue. See my answer for a larger explanation.
Have you made sure that in Server Explorer (In Visual Studio), if you right click on your connection that you have "Allow SQL/CLR Debugging" and "Application Debugging" checked?
Today, I finally solved this.
I was writing an ASP.NET application that included the line:
User.IsInRole("DOMAIN\\Administrators");
And this was throwing the following exception:
The trust relationship between this
workstation and the primary domain
failed
I wasted a little time applying the KB976494 hotfix, which I soon discovered didn't work. During my developer rage I looked in my local "Administrators" account and noticed it listed almost all members by their S-ID, so figured there may have been a domain problem.
Then it came to me... I remembered I joined the domain with my personal (non-administrator) account, instead of using the domain administrator account.
These were the ultimate steps to fix this issue:
Leave your domain (and join an arbitrary workgroup, such as "WORK")
Reboot.
Join your domain with your "DOMAIN\Administrator" account
User.IsInRole() now worked, so out of curiosity I checked this problem, and it was also fixed.
This is a great Friday so far!