Visual studio feeds

All Visual Studio blogs in one place

Subscribe

Enter your email address:

Delivered by FeedBurner

Increase your website traffic with Attracta.com

Google+

Contact

Email:
Subject:
Message:
Anti-spam: How many eyes has a typical person?

Follow us on FB

Search

ASP.NET Web API Basics

AddThis Social Bookmark Button
We have seen that now web is really becoming cross plate form and you can see your services or API can be exposed to any client. Till now one of big challenges is to choose platform for this kind of service. There are so many options available like web services, WCF services,Generic Handlers, directly writing responses on aspx page etc. There are plenty of options available and each one has their own pros and cons.  But now we have one simpler answer for that is ASP.NET Web API. What is Web API? ASP.NET Web API is a framework
for building web API on the top of .NET framework. It’s a framework for building and consuming web services that can be use at broad range of clients like browsers,tablets phones etc. You can expose JSON or XML whatever you want to use. Why to use Web API? Think about a situation where a jQuery script that is making a ajax request and we need some thing who can expose data from the server to the client at that time WEB API can be very handy you can expose server data in XML or JSON form and...(Read whole news on source site)

Code and Comments What is important

AddThis Social Bookmark Button
Being a programmer doesn’t make you great if you can write a long long lines of code. Its your baby you’ve got to put some thing in it so that other can understand it as clearly by looking at it. Nobody have time to debug the code every time as it takes time to setup the environment and debug your code. It would still remain a puzzle why you’re doing crazy things in it. Do you remember when you

My Favorite Features: Creating Storyboards with PowerPoint

AddThis Social Bookmark Button
In my last post on Continuous Value Delivery, I talked the importance of communication between the customer and the engineering team to arrive at a clear project definition. How many times have you built exactly what was asked for, but not what was wanted? Agile teams need the right communication tools to eliminate waste at this stage in the software lifecycle. In this post, I’d like to talk about PowerPoint Storyboarding, a new feature we built to help express and illustrate the intent of each item on the backlog. As the saying goes, “A picture is worth a thousand
words”. While working on my apps, I need a quick way to mockup UI and test different workflows before I start coding. I have PowerPoint on my machine, which I use all the time for presentations, so it’s quick and easy for me to mock things up there. In my case, these designs were primarily for my own review and brainstorming; however, this becomes even more valuable in a team environment where you can attach and link storyboards directly to items on the backlog. Building the Storyboard If you’ve downloaded the Visual Studio 11 Beta, you already have PowerPoint Storyboarding installed. Just fire...(Read whole news on source site)

Daily WP7 Development News 24 May 2012

AddThis Social Bookmark Button

VS2010 Large Solution Bottle Neck

AddThis Social Bookmark Button
  Recently I looked into speeding up Visual Studio builds – I found the results interesting… I decided to do a few POC’s to see where the bottleneck is with large solutions in Visual Studio. After some searching of the net I found various tweaks that one can do to ones machine to get better performance and a few mentions that VS2010 does not handle multiple project files very well – the number mentioned several times was 10 – if you have more than 10 projects in a solution you see a noticeable decrease in build time.
Solution with 100 projects each with a single class To validate this I set up a solution with 100 class projects with a single class in each project  and did a clean build. The average build time per project was 00:00.2 units, leaving me with a total build time of 00:16.0 units. Solution with one project and 100 classes in a single namespace The next step was to establish where the load was on the build, would I get similar results with a solution with one project with 100 classes. Again set that up – total build...(Read whole news on source site)

Home