I want to write a plugin to Visual Studio 2010 which changes the Office Communicator(OCS) status of a user when s/he startes debugging in Visual Studio. I am familiar with the Client-Side API of OCS but I can't seem to find a proper way to catch the DebugStarted event in Visual Studio.(I also don't know if it has one)
So, do you know any way to accomplish this?
Related
I am new to PowerShell and I am curious about its development in Visual Studio 2015.
In general, I was hoping that Visual Studio would show me available global functions defined in the project via autocomplete.
Is something like that even possible? It would be nice to have.
My team currently makes full use of Visual Studio Online team rooms to see when code is pushed to the server as well as track the chatter around it. I find having chatter in this environment keeps it on a more professional level.
In Visual Studio 2013 we were using a plugin to have this team rooms display directly within the Visual Studio application. Unfortunately this is no longer working with Visual Studio 2015 and I was wondering if there's a method for doing this out of the box that potentially I'm missing?
No, The us no way to get rid of of the box. You may want to email The Developers of the Plug-In that you were using and get them to update it.
I am trying to develop custom code for an InfoPath 2013 form. I have Visual Studio 2013 Professional installed, but when trying to edit code I get the following message:
The following external components are required to edit your form code. Please install them and try again.
Microsoft Visual Studio 2012
Visual Studio C# Support
Microsoft Visual Studio Tools for Applications 2012
C# support is installed, along with Visual Studio Tools for Applications 2012.
Does InfoPath 2013 just not support VS2013?
Unfortunately No
MS has really been making some bad decisions lately
Firstly VS2013 was released so they forced people to upgrade if you want to develop for Windows 8.1
Secondly, MS have announced that they are dropping InfoPath and have yet to provide an alternate solution. Support is still available but InfoPath 2013's successor will be another solution.....i'm guessing Azure Forms or SharePoint forms, something like that
Very disappointing
As you have found, adding code to an InfoPath 2013 form requires Visual Studio 2012. I am not aware of a way to use it with any other version of Visual Studio.
Depending on what you plan to use the custom code for, you may be able to get by with the qRules library (full disclosure: I am one of the developers of this library). It contains many of the most common features for which people tend to use code within InfoPath, and you can use them simply by executing rules within your form, eliminating the need for any version of Visual Studio.
If there is a specific thing you are looking to do with code, I can tell you whether it's possible to do so with qRules, but you should open a separate question for that (and let me know here).
I have a VSTO Word add-in that is built with Visual Studio 2010, in C# targeting the .NET 4.0 framework.
I have Visual Studio Ultimate 2010.
I also have a bug that no one in QA for the life of them can figure out how to reproduce -- it just happens sometimes -- we're pretty sure it's our code that's causing it -- but yeah, that's that.
What do I have to do, to make IntelliTrace run on a machine without VisualStudio and attach it to my add-in which is loaded by Word at run time and have it produce .ITRACE files that I can open with Visual Studio 2010 so that I can step through the code and see what's going on?
In Visual C# 2010 Express, if I type using S suggestions automatically popup:
In Visual Studio Express 2012 for Web using F#, if I type 'open S' nothing happens. I have to key ctrl-j in order to trigger suggestions:
Is there any way to get the former behavior in 2012? I.e. not have to type ctrj-j for suggestions, but have them come up automatically?
The C# and F# Intellisense implementations are written by different teams and have different goals. In general the F# experience is more minimal than the C# one. For items like open they won't automatically popup an experience and you must manually invoke it. There is no way to change this behavior.