There is another similar feature introduced in Visual Studio 2013, called Portable Class Library (PCL). Portable Library is also can be used by different project types. The main difference between these two kind of sharing options are:
- Shared Project share the code; whereas Portable Class Library share assembly(dll)
- Shared Project will not create any separate assembly; it will get compiled as part of the referring application. PCL compiles separately and add the dll reference to the referring project
- As shared projects are not precompiled, it can use with any kind of platform. PCL compiles in advance and won’t work with all platforms
Utilize the Shared Project in your solution to share the code and files among multiple projects. Create Shared Project using the “Shared Project” project template.
Visual Studio 2015 and TFS 2015 RC2 released on 20th July. The theme of the new product is ‘Choice’. As a developer, you can choose your programming language, your platform, and targeted device. You can choose to perform various tasks using integrated open source tools like JSLint. Build your code using your choice of steps and tools including Ant, Cheff, MS Build, and so on.
It was a great moment in listening to the product team and the demos showed by core team including Scott Hanselman. He created an ASP.NET web application in Windows; published the same to a USB drive. Plugged the USB to a Mac system and using DNX(.NET Execution Environment), packed as part of the new ASP.NET 4.6 application, deployed the same in Mac and run the web application. He open the solution in Mac using the new Visual Studio Code and edited.
Team demonstrated the great improvements and tool supports for debugging and performance monitoring. One of the demo is a remote debugging of a mobile application running on a device from Visual Studio running in laptop.
Another great improvement is Analyzers, small code snippet run behind while coding. It analyze the code and provide suggestions on the fly. Moreover, it provides the code blocks to fix the compilation issues.
Brian demonstrated DevOps implementation internally in Visual Studio team. Build system re-architecture address many new build systems and tasks. Build system management features including version control of build definition added to Web access.
Many new features and tools released as part of VS 2015 and TFS 2015 RC2 release. Some of the features are
- DNX – .NET Execution Environment to run the .NET application in any platform
- New build system
- Analyzers – Code time compilation issue detector
- Debugging improvements
- Performance monitoring tool improvements
- Quick integration with open source packages
- IntelliTest – Unit test framework analyze the solution and provide an exhausted set of input values and unit teste generation for future purpose
- Mobile Emulators – great emulators including beta support for Apple smart watch
Will post more on each of the new features soon
PerfTips is one of the new debugging feature introduced in Visual Studio 2015. This feature help the developer to look into the performance aspects at the time of debugging the code itself. This feature will help in fixing proactively the performance issues at an earlier stage; even without performing a complete performance test.
PerfTips will show the elapsed time taken from the last break point to the current break point, or the time taken to execute the method. This can be configured to display the CPU time taken by the code snippet. These tips will be shown as a small tool tip at the right side of the statement where you have the current break point.
When we do work item customization, we tend to add and remove new fields. Over a time, few fields which we added as part of initial work may not be used. But the unused fields will still appear in your Query editor field list.
Following Witadmin commands will help you to identify the unused fields and clear the same
Command to list all the unused fields
witadmin listfields /collection:http://tfsserver:8080/tfs/DefaultCollection /unused
Commands to delete the specified field say My.SumField
witadmin deletefield /collection:http://tfsserver:8080/tfs/DefaultCollection /n:My.SumField
If you want to double check, whether a field is used or not, use the following command
witadmin listfields /collection:http://tfsserver:8080/tfs/DefaultCollection /n:My.SumField
If it returns “Not In Use“, indicate the field is not used in the project collection
Use: Not In Use
Reportable As: None
Posted in TFS
Tagged TFS, witadmin
Millions of developer today turn to lightweight code editors and command-line centric development workflows as their primary application development environment. With Visual Studio Code, Microsoft introduced a new, free, cross-platform code editor for building modern web and cloud applications on Mac OS X, Linux and Windows, available in preview today. It supports IntelliSense (an intelligent code completion system), debugging, and GIT.
For more details