Skip to main content

What's New in Visual Studio 2017 RC

What's New in Visual Studio 2017 RC

We have many new as well as improved features and experiences in Visual Studio 2017 
to make you more productive at things you do every day

IntelliSense 

IntelliSense comes enhanced with added filtering that makes it much easier to use.
Filtering makes long lists much more manageable. With features like Camel Case search
you only need to type in the 2 letters in capitals for IntelliSense to appropriately filter
results for you that match 2 different words with those letters capitalized. IntelliSense
is also smarter now; it will select the best matching result from the list instead of simply
picking the top result.


Navigation

Navigation. Navigate To is much more powerful with better filtering and preview. 
We have also fixed Find All Reference by adding color, grouping, and a peek preview
in the Find All Ref window.







Live editing

One of the most useful features is live code analysis. As the name suggests it analyses
your code and flags issues in the editor. Live unit testing brings pass fail information right
into your editor. It not only tells you when tests are missing but with one click you can easily
create a simple scaffold of a unit test. Visual Studio will write the test, drop the test, and
immediately start running it in the background. These tests run in the background and notify
you of pass/fail status right in your code.
Opening files without projects
 In Visual Studio 2017 RC you can directly work on code bases and files without any association
with projects or solutions. Simply navigate to a folder from the menu File > Open > Folder and
select the file.
Debugging
 With Run to Click there is no need to set temporary breakpoints. Once you start debugging you
will see a green glyph on the left. Simply click on it to run your code till that point. You will also
see another glyph on the right. This is for perf tips and is very helpful in identifying perf issues
immediately. If the perf doesn’t look right simply click on the glyph to open the diagnostics tools
window to solve the performance problem you just found.


Code Analysis 

Visual Studio 2015 introduced the live code analysis feature, which enables
“as-you-type” feedback on your code. This lets you learn about issues early, before
they build, rather than accumulating a set of problems you might never get around
to fixing. To resolve the errors identified in live code analysis, you use the lightbulb
menu or the shortcut “Ctrl+.” to access code fixes and refactorings.
   
Visual Studio 2017 RC takes live analysis and code fixes a step further by amplifying
the set of refactorings and code fixes available, and by introducing code style
analyzers that identify style issues in code as soon as they’re typed.
Visual Studio 2015 included some core refactorings: extract method or interface,
change method signature, inline temporary variable, introduce local variable, and
remove unnecessary usings and imports. Visual Studio 2017 RC expands the set of
refactorings and fixes to help you maintain a readable code base and catalyze your
development workflows. For example, a significant number of developers initially
write all their classes, interfaces, and other types in a single file and then extract each
type into a file with the matching name later.
 Visual Studio 2017 RC expedites this process with the refactoring option
“Move Type To Matching File.” Other refactorings you can look forward to include:
  • Sync file and type name
  • Convert property to method
  • Use object initializer
  • Convert null-check + throw to use ?? + throw
  • Convert string.Format to interpolated string
  • Make method synchronous
  • Add missing case
  • Add braces
Additionally, this release introduces some basic code analysis and fixes for XAML.
Using the same lightbulb mechanism in C# and Visual Basic, you can sort and remove
 unnecessary name­spaces and add missing namespaces in your XAML files. 

 New shortcuts in VS 2017 RC


Go To DefinitionPeek DefinitionFind All ReferencesGo To ImplementationGo To All (File/Type/Member/Symbol)
F12Alt+F12Shift+F12Ctrl+F12Ctrl+T or Ctrl+,

Comments

Post a Comment

Popular posts from this blog

Claims Class For security in .NET4.5 with C#

What is Claim ? A claim in the world of authentication and authorization can be defined as a statement about an entity, typically a user. A claim can be very fine grained: Ram is an admin Ram’s email address is Ram@yahoo.com Ram lives in Mumbai Tom’s allowed to view sales figures between 2009 and 2012 Tom’s allowed to wipe out the universe Claims originate from a trusted entity other than the one that is being described. This means that it is not enough that Tom says that he is an administrator. If your company’s intranet runs on Windows then Tom will most likely figure in Active Directory/Email server/Sales authorisation system and it will be these systems that will hold these claims about Tom.  The idea is that if a trusted entity such as AD tells us things about Tom then we believe them a lot more than if Tom himself comes with the same claims . This external trusted entity is called an  Issuer . The KEY in the key-value pairs is called a  Type  and the VALUE in the
1 comment
Read more

Paytm integration

How to integrate Paytm to asp.net site   You will need to create an Checksum on your server. Kindly refer the dll file for the attachment.  Usage of CheckSum API: ·         Add provided “paytm.dll” as a “Reference” in your project. ·         Import namespace “paytm” in your Class with statement “using paytm”. ·         Now Generate CheckSum API as well as Verify CheckSum API are available as follows: o   String CheckSum.generateCheckSum(String masterKey, Dictionary<String, String> parameters) o   Boolean CheckSum.verifyCheckSum(String masterKey, Dictionary<String, String> parameters, StringcheckSum) ·         For Generating CheckSum, use following snippet code: String masterKey = “merchantKey” ; Dictionary<String, String> parameters = new Dictionary<string, string>(); parameters.Add("CHANNEL_ID", "WEB"); parameters.Add("TXN_AMOUNT", "1"); String checkSum = CheckSum.generateCheckSum(masterKey, parameters); ·        
Post a Comment
Read more

Design Patterns

                                                      Design pattern 1. Factory Design Pattern  In Factory pattern, we create object without exposing the creation logic to the client and refer to newly created object using a common interface. Step 1 Create an interface IShape.cs public interface I Shape { void draw (); } Step 2 Create concrete classes implementing the same interface. Rectangle.cs public class Rectangle : I Shape { @Override public void draw () { C onsole.WriteLine ( "Inside Rectangle::draw() method." ); } } Square.cs public class Square : I Shape { @Override public void draw () { C onsole.WriteLine ( "Inside Square::draw() method." ); } } Circle.cs public class Circle : I Shape { @Override public void draw () { C onsole.WriteLine ( "Inside Circle::draw() method." ); } } Step 3 Create a Factory to gen
Post a Comment
Read more