I want to create a custom extension, i.e. to add a button to the test runner in MTM. Is it possible to do so, like with a VSIX extension, in the same (or similar) way as can be done with Visual Studio?
More info:
What I want to create is a plugin for MTM, that will add a button to the Test Case editing window (under the Testing Center | Plan section), that when pressed will do something (e.g. generate some code).
UPDATE
I looked at what TestScribe does, and after installing it, a third center is added (after "Testing Center" and "Lab Center") - Tools (see below):
I will be very happy, if I can somehow add a tool much like Documentation above.
You can customize like Test Scrib on MTM, you can get the code on Codeplex, but I don't know if you can customize the panel screen of the runner... Give more detail what you want.
Related
I am using the VS 2010 to create a setup project, I am going to use the TextBox(A) dialog to capture user input.
I would also like to validate inputted value in these text box. Something likes the Next button just be enabled only when the first text box meets a specific criteria. So that, the installer just navigates user to next page when the validation passed.
Is it possible with the VS 2010?
There's no support in VS setups for doing this. It's a feature that's available in other tools and is part of Windows Installer, so you'd need to use another tool to add that functionality to the setup.
I know its not the exact you need but it will gives you idea on how to parse the value during install. See the following link in Scott Guru Blog
and post the solution if you find because for that sake i am now developing a click once application.
Visual Studio has a feature called Custom Tools. The Custom Tool will run every time I save a file or, if I click the "Run Custom Tool" menu item. Is there a way to make it run only when I click the Run Custom Tool menu item?
I don't believe there is any way to discriminate from within the custom tool code. This may be stating the obvious, but it sounds like a normal VS add-in would be more appropriate in your case.
I want my setup progress window look like Visual Studio's installation's progress window, i.e, show list of features, and show text or image as one by one feature installation completes...!!
This can be done through a billboard control: http://kb.flexerasoftware.com/doc/Helpnet/InstallShield2011/IHelpEUDialogsBillboard.htm
Basically, you define multiple billboards and configure them to be show during install.
I want to achieve that when the user installs the WP7 control library he will find it in the Visual Studio toolbox automatically without manually adding it. In addition I would like to organize toolbox tabs in a logical manner.
I know it can be done for other platforms. For example I tried writing *.design.dll as described here - it does not work for WP7.
Any pointers how to work with toolbox for VS 2010 / WP7?
Nobody answered, so here is my brief summary:
The control library cannot be added to the Toolbox automatically unless you program VS plugin (package). Too much work for me...
*.design.dll (see the link above) basically works.
2a) You can hide controls from the Toolbox (BrowsableAttribute) and you can define control icons. That's probably everything you can do for Toolbox. The user has to add Toolbox tabs and "choose items" manually.
Well, I am not quite sure here, because when you drop the control dll file onto the Toolbox, then at least ToolboxTabNameAttribute works, i.e. corresponding Toolbox tabs are created automatically. Unfortunately, the tab is empty.
Also, when the control library is properly installed, then some of the controls are added to Choose items Toolbox dialog. Unfortunately, in my case most of the controls are missing and have to be added by manual browsing.
2b) Designer support (Properties window for the control) is better. You can hide properties (BrowsableAttribute), define categories (CategoryAttribute) and define descriptions (DescriptionAttribute).
Descriptions can be extracted from you documentation xml file, so that you don't need to write them again. To get the code google for MetadataBase.cs. Just be carefull, the files you'll find contain fatal bugs (ParseDescription method) and ignore some properties (getters that return a collection).
After all, the result is not that bad.
Unfortunately it looks like for various reasons I'm going to have to use Visual Studio 6 instead of a newer version of VS.
It's been a long time since I've used it. I'm looking through its menus and don't see any obvious way to set up any custom build steps (pre-build, post-build, pre-link... anything would help actually).
Can anyone give me instructions on how to set up steps like this?
Open your project, then open the Project Settings screen (Project → Settings or ALT-F7). Alternatively, right click on a file in the FileView and select Settings.
From the Project Settings screen, go to the General tab and check "Always use custom build step". This means that the file you just chose will be an input file for a custom build step. From the "Custom Build" tab you can then give the commands to run and specify what files will be generated.
For pre-link, post-build and such, select an executable (or library) from the Project Settings screen. Then use the little arrow button to scroll to the rightmost tabs. From there you'll find the Pre-link and Post-build steps.
It's quite simple, really, I'm sure this is enough to get you started.