Visual studio feeds

All Visual Studio blogs in one place


Enter your email address:

Delivered by FeedBurner

Increase your website traffic with



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

Follow us on FB


How to Share Status from WP7 using the ShareStatusTask?

AddThis Social Bookmark Button
Do you want to develop an application or game which will update your status or game result in some social networking sites like Facebook, Twitter, Linked-In and/or Windows Live? Then this post will help you to integrate such task in your app.   Using “ShareStatusTask” of the Windows Phone 7 SDK, you can update your status line on the social networking sites. Continue reading the post for more details of the API and the implementation steps.   Know About the API “ShareStatusTask” is a sealed class present in the namespace “Microsoft.Phone.Tasks” and inherits
the class named “ShareTaskBase”. ShareStatusTask exposes a string property called “Status” where you will set the message that you want to share on social networking sites.   Here is the meta data of the ShareStatusTask:     namespace Microsoft.Phone.Tasks { public sealed class ShareStatusTask : ShareTaskBase { public string Status {......(Read whole news on source site)

Saving View State in Cache

AddThis Social Bookmark Button
Most people who have worked with ASP.NET web forms know about view state; they may have both benefited from and cursed it, since it allows simple things to be done very easily but also as easily doing very stupid things, like filling up an HTML page with several megabytes of data which have to be submitted on each postback. What some people won’t know is that the way the view state is maintained is extensible and based on a provider model. Besides the default way of storing view state in an hidden field, ASP.NET includes another implementation of the
provider which allows state to be stored in the session, thus keeping it out (but for a small part) of the HTML. The abstract base provider class is PageStatePersister and the two included implementations are HiddenFieldPageStatePersister and SessionPageStatePersister. So, what keeps you from storing everything in the session? It seems like an easy choice… there are some drawbacks, however: All browser tabs share the same session, so care must be taken if the same page is open on two tabs, because changes to the session made in one page will affect...(Read whole news on source site)

We Want YOUR Windows 8 Metro style Apps!

AddThis Social Bookmark Button
With the Release Preview of Windows 8 coming in June, it's time to get cracking on your apps. If you haven't already, you should download the Windows 8 Consumer Preview, and the Visual Studio 11 Beta and start working on an app. If you're already working on an app, you may have heard that at present, you need a token to get access to submit your app to the Windows Store. So how do you get a token? I'll leave the answer to my fellow Microsoftie Jaime Rodriguez: It’s easy! If
your app is ready and you want to be among those developers who get to submit to the store early, simply attend one of the 100s of free Application Excellence Labs that DPE and Windows are holding around the world. Follow these steps to get invited to an App Excellence lab: Create a really great Windows 8 Metro style app (or game) immediately. Get it as ready as if you were submitting to the store. If you know your local DPE evangelists (maybe because you attended a Windows camp training), get in touch with them and ask...(Read whole news on source site)

ICommand issue in Windows 8: Correction!

AddThis Social Bookmark Button
Well I'll be… I stand corrected! I recently published a blog post stating that you need to declare a command as ICommand (instead of RelayCommand) if you want it to work in Windows 8. I even went as far as to modify the MVVM Light code snippets that are used to create commands. In fact, scratch that post… I was wrong! I got a few people writing to me and letting me know that RelayCommand works just fine for them. And now, after I tested again, I cannot reproduce the issue! So I need to be
clear, my first post was wrong, and I stand corrected. Based on the feedback, I will also set the MVVM Light snippet back to expose the command as RelayCommand instead of ICommand. It would indeed be "purer" as ICommand, but it also causes issues (such as the need to cast to call RaiseCanExecuteChanged) and is not worth it. Sorry about the confusion folks!! Cheers,

How to Create an ASP.NET Wizard Interface in ASP.NET MVC & WebForms

AddThis Social Bookmark Button
Check out this slick Code Central example on how to create a Wizard interface in ASP.NET using DevExpress ASP.NET controls. First, here's a glimpse of what it looks like: Pretty cool, huh? And it works for both ASP.NET MVC and WebForms! Check out the Code Central solutions here: ASP.NET WebForms - How to organize Wizard interface within ASPxPageControl ASP.NET MVC - How to organize Wizard interface within ASPxPageControl and ASPxMenu Learn how use Code Central by watching
this tips video How's it work? This wizard interface is a great example because it uses several of the controls from the DXperience ASP.NET subscription:
ASPxPageControl, ASPxPopupControl, ASPxMenu (part of ASPxperience)
ASPxCheckBox, ASPxLabel, ASPxTextBox, ASPxDateEdit, ASPxComboBox, ASPxButton, ASPxValidationSummary (part of ASPxEditors) At the heart of the sample, the ASPxPageControl controls the views before the end-user can move forward to the next view. And the DevExpress ASP.NET editors will ensure validation before...(Read whole news on source site)