Announcing the Visual Studio 2013 Release Candidate
I’m excited to announce the Release Candidate of Visual Studio 2013, .NET Framework 4.5.1 and Team Foundation Server 2013! The release is available for download now on the Visual Studio product website and is a "go-live" release. Starting today, developers can also download Windows 8.1 RTM via their MSDN and TechNet subscriptions.
The RC release is the next big step toward the release of Visual Studio 2013. Today I am also excited to announce that Visual Studio 2013 will RTM at Windows 8.1 GA and the Visual Studio 2013 Virtual Launch will be held on November 13th, 2013! Available online around the world, more details can be found on the virtual launch event on the events page.
Trying out the Bits
The Visual Studio 2013 RC can be installed on top of the Visual Studio 2013 Preview or side-by-side with Visual Studio 2012. Please note that Windows Store app development with Visual Studio 2013 RC requires Windows 8.1 RTM, which is available to MSDN and TechNet subscribers, starting today. (Visual Studio 2013 RC does not support Windows 8.1 Preview or Windows Server 2012 R2 Preview.) For Windows Azure developers, the VS 2013 RC supports the same July Azure SDK (version 2.1) as the VS 2013 Preview.
For more details, see the Visual Studio 2013 RC system requirements and platform compatibility site.
New Features in the Visual Studio 2013 RC
Visual Studio 2013 contains great new features for developers across all Visual Studio languages and platforms. I talked about many of the new features in my post on the Visual Studio 2013 Preview in June. Features like synchronized settings, peek definition in the editor, UI responsiveness tools for XAML and HTML apps, async debugging, and Azure Mobile Services integration provide enhancements across a wide range of developer scenarios.
Today, I’ll take a look at a few of the features that are new to the Visual Studio 2013 RC release. For even more on Visual Studio 2013 RC, check out the “What’s New” page.
XAML Editor
One of my favorite improvements in Visual Studio 2013 RC is the enhancements to the XAML editor. Developers are authoring XAML for many of our platforms, from WPF to Silverlight to Windows Phone to Windows Store.
In the RC, we’ve added IntelliSense for Data Binding to the XAML editor. This works with a DataContext defined in the markup, or with a design-time DataContext for cases where the context is provided in code-behind.
We’ve also added support for Go To Definition for Resources, Bindings, Properties and XAML Elements. For example, if you Go To Definition on a Resource:
You are taken to the definition of that Resource.
For much more detail on these improvements, see Harikrishna Menon’s post on the Visual Studio blog: XAML Editor Improvements in Visual Studio 2013.
Cloud Business App
At the Build conference in June we provided an early glimpse into how Visual Studio will enable the next generation of business applications using the Microsoft cloud. The ability to build modern business applications that use the power of Office 365 as part of your application is now available in the Visual Studio 2013 RC through the Office 365 Cloud Business App template.
The Cloud Business App template is powered by the same technologies as LightSwitch which provides unparalleled developer productivity through RAD experiences with the flexibility to write code when you want to. This includes the ability to quickly and easily attach and consume data from multiple data sources and to define your own entities. By default, without writing any code, Cloud Business Apps extend the Office 365 experience enabling your apps to facilitate collaboration and enable communication, and they provide an HTML based app UX that works great across the desktop and devices.
The Visual Studio 2013 RC is just a small sampling of how the Office 365 Cloud Business App template will enable developers to build modern business applications that extend the Office 365 experience and build upon the capabilities of Office 365 and Windows Azure. There is much more to come in RTM, stay tuned.
My previous post from Build 2013 has more details about the Cloud Business App feature and vision.
C++
During the Build conference, I wrote about the roadmap for C++ standards conformance in Visual C++. Last week at the Going Native conference in Redmond, we hosted a great discussion about the present and near future of modern, standard C++, and talked about what’s coming in Visual C++ and C++ on Microsoft's platforms. In Visual Studio 2013 RC, we’ve made more steps along the roadmap laid out at Build, adding C++ 11 features like using aliases, = default and non-static data member initializers.
For more details, check out Herb Sutter’s “The Future of C++” talk from Build.
TypeScript
Less than a year ago, we released the first public preview of TypeScript, a language and tools for application-scale JavaScript development. With Visual Studio 2013 RC we are including the most recently released version of TypeScript tooling (v0.9.1.1) as we continue to seek community feedback from our early adopters.
TypeScript brings classes, modules and optional static types to JavaScript development. In Visual Studio, this enables rich tools like live error reporting as you type, IntelliSense, and Rename refactoring.
For more information on TypeScript, check out the TypeScript site and blog.
CodeLens
I’ve noticed as we’ve shown Visual Studio 2013 to developers, one of the most head-turning new features is CodeLens, a Visual Studio 2013 Ultimate feature which provides deep contextual insights inline in your source code. CodeLens for C# and Visual Basic provides information such as the number of references, and recent changes from source control.
In the RC, deep Lync integration has been added, so you can easily contact the developer who most recently worked on a piece of code directly from the Visual Studio editor. Several new indicators are also now available exposing Bugs, Work Items and Code Reviews related to the class or member, for developers working with source code in Team Foundation Server 2013.
More details about the CodeLens feature are available on MSDN.
Work Item Charting
In both Team Foundation Server 2013 RC and today’s update of the Team Foundation Service, we’ve added a new Charts feature to Work Item tracking. Work Item Charting enables developers to quickly create charts to visualize data from work item queries. These charts can be created with just a few clicks and refresh automatically as data is updated.
For more information on this feature and other updates to TFS, check out the TFS release archive.
Feedback
We made hundreds of fixes in the RC based on feedback on the VS2013 Preview release. I encourage you to download the new bits and send feedback to the team:
Feedback can also be sent directly from the product, using the menu in the top-right corner of the IDE.
Conclusion
The Visual Studio 2013 RC is the next major step toward the Visual Studio 2013 release and the launch on November 13th. Download the bits, and register for the launch today!
Namaste!
Comments
Anonymous
September 09, 2013
Wonderful! I was not expecting this so soon, mainly Windows 8.1! Just a simple question: will VS 2013RC be directly upgradable to Nov 13 RTM version? Congratulations.Anonymous
September 09, 2013
@Abel - Details about RC to RTM upgrade are on the System Requirements and Platform Compatibility page near the end: www.microsoft.com/.../compatibility-2013Anonymous
September 09, 2013
... actually I'm afraid a lot of feedback is ignored ... loads of requests to continue development of Silverlight (even only in bug-fixing/maintenance mode would be acceptable) and eventually allow it to run in Win8 Modern UI are constantly ignored. Do you really think anyone who's developed a serious LOB app will ever port it to Win8.1/2/3/n? It's almost impossible technically and cost prohibitive given the almost non-existent adoption of Win8 in enterprises. Having Silverlight running in Win8 (in whatever way, through winstore or just IE) would give you instant productivity apps that would help tremendously adoption of Surface tablets in enterprises.Anonymous
September 09, 2013
You guys really don't hear the community. It's sad. I'll stick to Vs2010... visualstudio.uservoice.com/.../3041773-bring-back-the-basic-setup-and-deployment-project-Anonymous
September 09, 2013
CodeLens is another Ultimate-only feature? Great. Looks like another feature that 95% of your user base won't have. There really is no excuse for the insane price of the Ultimate version of this software; it has a lot of nice-to-haves, but nothing that I could justify to management spending $13000 per developer on. Apple and Google gives their dev tools away for FREE. You guys hurt the whole Microsoft ecosystem you're trying so hard to protect by putting your tools behind these huge paywalls.Anonymous
September 09, 2013
I can't agree more with MgSm88, it's insane to release CodeLens only for Ultimate. I really don't understand the rationale of the product manager for such decision, it's like a bunch of people out there are on a course to transform VS in a tool dedicated to few zealots ... is this the new strategy? nothing can actually come as a surprise today in the world of MS.Anonymous
September 09, 2013
Is it worth spending time on improving comments in XAML editor or developing this CodeLens feature rather than Silverlight 6? visualstudio.uservoice.com/.../3556619-silverlight-6 - votes are added daily!!!Anonymous
September 09, 2013
The comment has been removedAnonymous
September 09, 2013
Huge fan here but I must express disappointment that Code Lens didn't make it to Premium.Anonymous
September 09, 2013
Good news.Anonymous
September 09, 2013
Please, give us excepted prices, especially for those who bought vs 2012Anonymous
September 09, 2013
Hi, do you have any information, when we can upload our new or updated Windows 8.1 apps to Windows Store? ThanksAnonymous
September 09, 2013
The comment has been removedAnonymous
September 09, 2013
Can I upgrade from the Preview, or do I have to uninstall the preview first?Anonymous
September 09, 2013
The comment has been removedAnonymous
September 09, 2013
Silverlight is dead, get over it. HTML + JSON + TypeScript is a much friendlier environment to code in.Anonymous
September 09, 2013
@Yaakov: to just "code" probably, but how about testing and maintaining that code? Or modularity?Anonymous
September 09, 2013
This is great progress. Thanks for mentioning the business applications advancements!Anonymous
September 09, 2013
Silverlight ist clinical dead. Google develops native client further. I understand the the importance of win 8.1 and phone 8.1, but give us at least a way we can migrate our products. Give us async on WCF client, give us TPL and support Win RT. PS: we have clients on Win XP and our clients will have Win 7 for next 5-7 years. Rewrite is not a solution for many of us in enterprise software sector.Anonymous
September 09, 2013
Did you fix the GUI? Did you bring back setup and deployment projects?Anonymous
September 09, 2013
Woop! Nice!Anonymous
September 09, 2013
It would be good to see tips on migrating an 8.0 app to 8.1 (especially tips around losing LayoutAwarePage and other 'common' based featuresAnonymous
September 09, 2013
Have you restore the setup and deployment project ? visualstudio.uservoice.com/.../3041773-bring-back-the-basic-setup-and-deployment-project- We will never change version until we have it backAnonymous
September 09, 2013
@Florin: I would get your comment about maintenance had you talked about JS. With TS it's a whole different story. Try it if you hadn't. SL encourages fat protocols (WCF) and heavy clients (XAML) that require a plugin. It made some sense few years ago, but now the browsers are much faster and compatible with each other. It was a nice try, but it no longer makes sense. SL developers should realize it and advance their careers in true web technologies.Anonymous
September 09, 2013
The comment has been removedAnonymous
September 09, 2013
I had Visual Studio 2013 Preview installed and was able to connect to TFS2008, after upgrading to Visual Studio 2013 RC, I no longer can connect to TFS2008. I get the following error: "TF205020: Could not connect to server ‘*****’. This server was used in your last session, but it might be offline or unreachable. Confirm that the server is available on the network. To attempt to connect again, or to a different server, click ‘Connect To Team Foundation Server’ in Team Explorer or the Team menu. The server returned the following error: Object reference not set to an instance of an object." Restarting VS or Windows does not fix the problem.Anonymous
September 09, 2013
From today's www.reuters.com/.../us-microsoft-ceo-idUSBRE98904K20130910: "Its online and mobile computing efforts do not make money. Its Bing search engine and other online ventures have lost almost $3 billion in the last two years alone, and last quarter the company took a $900 million write-down on the value of unsold Surface tablets. Despite billions of dollars of investment, Windows phones still have less than a 4 percent global market share, according to the latest figures from research firm IDC." ... while a small team to keep Silverlight alive even in bug-fixing/maintenance mode wouldn't cost MS more than few millions. Even if you release updates once every year is more than acceptable. All that amount of money that MS is wasting on 3-different-platforms-to-run-angry-birds must come from somewhere. And it comes from people who create reliable software everyday in enterprises. The needs of enterprises go beyond the hype-factor of HTML5, the minimal object-orientation brought by TypeScript and other-hundreds-of-JS-frameworks and beyond the thin client. In general people who have not been exposed to genuinely complex problems of financial services, medical environments, aviation, automotive, industrial machinery should not really be allowed to judge on technical strategy or development frameworks used in these fields. And so far win8 ecosystem does not offer absolutely anything to enterprises, MS has not found a way to bring the touch experience into enterprises and I really doubt that win8 is the answer (and I did research it, it's just a toy for games on tablets, and the limited capabilities of apps offer almost nothing even for desktops with touch screens . Maybe win 8.4 or maybe win 9 or whatever, but it is a very long way to go. Till then we need to continue to create applications that make a difference in people's lives and be able to run them easily on MS and Apple desktops. And very decent touch experience can be implemented already in Silverlight, and you can improve it to bring it on a par with latest gestures, etc. ... not to mention that if Silverlight applications are ported to HTML5, accepting all sorts of limitations and massive development costs, the winstore will never benefit from them in any way!!! Serious Silverlight apps cannot be ported to Win8 because it is often impossible due to serious development costs, and most of the time those people who run and pay for these SL apps don't run Win8 - simply because there is nothing else in the ecosystem that they need (these people don't need angry-birds I'm afraid). While I appreciate and have lots of respect for MS investing into the mobile area ... I'm afraid it cannot simply ignore (hurt in the case of Silverlight) those people in enterprises that pay lots of money for tools and services that allowed MS the luxury to invent 3 distinct, non-interoperable mobile frameworks to run angry-birds. Sometimes, just like in a marriage, a bit of attention or care will make a lot of difference.Anonymous
September 09, 2013
Agree with MgSm88....adding fluff that no one will buy or use doesnt justify moving to VS 2013. Likewise, trying to generate revenue from a tool when your competition is giving theirs away for free and instead focusing on revenue from the production and publishing of applicaitons is a bad business model.Anonymous
September 09, 2013
Similar to Jason W, I can't connect to our TFS server with the RC version - the previous "preview" version was OK. In my situation I can enter the details of our server in the "Add Team Foundation Server" dialog - and presumably it finds it because when I enter rubbish it displays a suitable error dialog, however, the server doesn't then show up in the Add/Remove Team Foundation Server dialog's list.Anonymous
September 10, 2013
@Ian: We do have a blog post that documents migrating Windows 8 apps to some of the newer constructs available in Windows 8.1: blogs.windows.com/.../windows-8-to-windows-8-1-preview-starting-with-the-xaml-templates.aspx Please do let us know if you run into any issues during migration.Anonymous
September 10, 2013
Hi, what are the limitations with the preview and RC versions? Can I still use it after the product launches?Anonymous
September 10, 2013
VS 2013 RC installs just fine over the preview on Win 7 Ultimate 64-bit. Same for Win 8.1RTM. No installation issues at all. Nice work.Anonymous
September 10, 2013
I'm having a similar issue to Jason W as well. After the upgrade I can no longer connect to TFS 2008. I can no longer use VS 2013 as a result. :-(Anonymous
September 10, 2013
The comment has been removedAnonymous
September 10, 2013
The comment has been removedAnonymous
September 10, 2013
The comment has been removedAnonymous
September 10, 2013
The comment has been removedAnonymous
September 10, 2013
I assume CodeLens requires you to be using a TFS workspace, and won't work with git-tf?Anonymous
September 10, 2013
Do you wanna lose everything you've built in last 20 year? You are on the best road!Anonymous
September 11, 2013
The 2012 trial download page redirects you to the 2013 RC page. Can the 2012 trial download page be fixed to stay on the 2012 trial page? Our commercially sold software product cannot be moved from VS 2010 to a pre-release version of VS. www.microsoft.com/.../downloadsAnonymous
September 11, 2013
This release is a bunch of garbage !!!!!!! Why aren't you listening to what developers want !?!?!?!?!? Your blog is nothing more then what you hope this product will be like, do you even use Visual Studio ? The best news you can give us in your next blog post is your are leaving with Ballmer and taking the rest of the VS team with you!Anonymous
September 11, 2013
@Ralph - All of the downloads on the 2012 trial downloads page you linked to appear to correctly link to 2012 downloads. There is also a cross-reference to the 2013 RC for those interested in trying 2013 as well.Anonymous
September 11, 2013
@Joe White It's true we don't have support for Git at this time for CodeLens. Unfortunately, we just ran out of time. Luckily, there is more time to be had :).Anonymous
September 11, 2013
Who is going to pay $2000+ a year now just to constantly upgrade VS?Anonymous
September 12, 2013
The work item charting feature is great - I do think the next release should consider charting for Queries that return hierarchies - for example to chart stories in Closed / Resolved state which have Test Cases linked to them in Ready/Design state.Anonymous
September 13, 2013
The comment has been removedAnonymous
September 13, 2013
The comment has been removedAnonymous
September 13, 2013
@Jason @David @Robert Thanks for reaching out to us about the issues that you've experienced while trying to connect to a TFS 2008 server from VS 2013 RC. For the VS 2013 release, we no longer support TFS 2008, and the symptoms that you are seeing are the result of this lack of support. To work around this issue, you can use either VS 2012 (which can be installed on the same machine side-by-side with VS 2013) or upgrade the TFS 2008 server to a supported version (i.e. TFS 2010 or higher). Despite this lack of support, it is clear that we should improve the experiences when attempting to connect to an unsupported server, and we are in the process of making the necessary changes for the RTM release. You can expect to see a clear message informing you that the server is not supported and helping to work around the problem. In the future, we are planning to be more proactive in showing these types of actionable messages when a client or server is unsupported. If you have other questions about client-server version compatibility for VS and TFS, visit the compatibility topic on MSDN: msdn.microsoft.com/.../dd997788(v=vs.120).aspx One very important note about this topic - currently, VS 2013 is listed as "not supported" when attempting to connect to TFS 2010. However, the community response regarding the lack of TFS 2008 support has led us to re-evaluate our criteria for choosing to end support for server versions. As a result, we will continue supporting TFS 2010 with VS 2013. We are in the process of validating the compatibility between VS 2013 and TFS 2010, and we plan to make the necessary improvements to enable a good developer experience.Anonymous
September 13, 2013
@Matthew Mitrik (MS) adoption. blocker. (oh well, I guess our git migration is happening sooner rather than later)Anonymous
September 14, 2013
What happened to the Datarepeater in VS 2013 RC?Anonymous
September 16, 2013
The comment has been removedAnonymous
September 16, 2013
@Dave: can't agree more. I'm not touching win8 either. The situation in the market is pretty simple to me. Until very recently MS had (probably still has) the largest and probably strongest community of developers compared to Apple and Google. Everyone would expect that these developers would easily create hundreds of thousands of apps in 2 years ... yet it doesn't happen and it's getting worse! MS, my guess is that developers don't accept anymore to be treated as "baits" for your marketing-driven experiments originated out of clueless executives. Instead of incrementally moving existing frameworks like Silverlight and WPF into a more touch centric OS, you "strategically" decided to re-write everything and push it down the throat of developers. It does not work! Secondly, even if serious developers would consider win8 on its merits, one can quickly find out that it does not solve real problems. I will say it again (after researching what win8 offers), it's just a copy-cat framework after apple/android to create kids games and apps. Does the world really need a third major framework to run angry-birds?? I guess no ... otherwise that strong developer-oriented ecosystem would have created way more apps, lots of enterprise Silverlight apps would have been ported. So the answer is a BIG "NO" to win8.Anonymous
September 16, 2013
The comment has been removedAnonymous
September 16, 2013
I have to agree that the current direction MS is pursuing, Windows 8 and their cloud services, are looking like a complete dead end for the company. They had a chance to make it all work, but appear to have decided to ignore the feedback, put their heads down and try and bury us in barely stable, poorly designed and limited feature software releases as a way to push us to their cloud services. If they had released an improved desktop version of Windows 8, as opposed to the gutted monstrosity they are currently trying to push, that maintained the strengths of the Windows 7 UI along with many of the core improvements, then I think they would have had a winner on the desktop. The only platform that the current Intel Windows 8 version really appears to work for is the touchscreen ultrabook form factor. I actually love my HP touchscreen ultrabook with Windows 8. While I must admit their are only a few Store apps I find remotely usable, the desktop experience is more than acceptable for any of the legacy applications on the smaller screen. I have the Lenovo Thinkpad T2 tablet that has good, but not great, performance for the form factor. Unfortunately I just cannot get comfortable enough with it for anything beyond web browsing and even for that I must make a lot of compromises. Last night I surfed for an hour using the T2 and then picked up an original ASUS Tranformer Android tablet and found the browsing experience to be much smoother and without all the crashing tabs that IE 10/11 experiences. Personally I am looking forward to trying the upcoming 7 inch tablets as this is where I think the shortcomings of the store apps will not be as apparent and some OEM's could create some truly innovative packages. My dream Windows 8 tablet is a 7 inch screen running Windows Phone 8 but with enough horsepower to be dropped into a dock and used for basic productivity applications, office/web/meetings/skydrive, while providing a phone UI so that, when combined with a Bluetooth earpiece, a complete all-in-one mobile solution is available at home, in the office and on the road. If the current rumor is true and Nokia is delaying/cancelling their 6 inch phablet because of the MS buyout, I will likely be getting an android phablet while MS decides what they are going to do with their new toys, and try writing a few apps for their OS. But none of this will come to pass if MS keeps trying to force developers to work in an IDE they hate to create apps using API's they find... lacking. Perhaps once the re-org starts to wind down there will be enough new blood in place that can change course, without fear of reprisal, because they were not involved, or at least no longer in the same position, in creating this debacle. We can only hope, but for now I am hedging my bets and spending my personal training time adding depth to my skills on other platforms.Anonymous
September 16, 2013
Please, fire workers and managers who Declined to bring back Setup and Deployment projects: visualstudio.uservoice.com/.../4434972-please-fire-workers-and-managers-who-declined-to-Anonymous
September 22, 2013
Will it be possible to upgrade 2013 RC to the RTM version?Anonymous
September 23, 2013
@Peter - Details about RC to RTM upgrade are on the System Requirements and Platform Compatibility page near the end: www.microsoft.com/.../compatibility-2013Anonymous
September 25, 2013
congratulation...............................Anonymous
September 25, 2013
IMMEDIATELY THIS SOFTWAREAnonymous
September 27, 2013
Instead of providing tools to manage obscene amounts of code written upon out of control frameworks ( hmm .GARBAGE) why not give us tools and environments that handle much of the code for us so we can focus on business logic that meet our client's needs instead of plumbing code and patching Microsoft's poor written compilers. What a novel concept, too bad it was developed in the 1990's therefore I can't take credit for it. Even worse this was buried by Microsoft with Visual Studio. Soma's greatest accomplishment is successfully moving software development back in time while devouring developer productivity in the process.Anonymous
September 27, 2013
Your site does not work right on android ...sorry I am not one of the four people that use windows phone .... what What an embrassment to microsoft when the vp of dev tools site is broke ... this speaks volume to the quality of your work while demonstrating the capabilites of visual studio and .net... complete incompentence.....Anonymous
October 09, 2013
This blog just showed up in the RSS feed in Visual Studio (9 Oct 2013). Barely more than 1 week from RTM, it's a bit of a waste of time asking for users to install the RC and ask for feedback because clearly none of it is going to influence RTM.Anonymous
October 09, 2013
@Gigaplex - It looks like this post was exactly one month ago on September 9th. I believe like the Visual Studio feed has had this post since then as well (it's dated as September 9th in that feed). If it just appeared recently for you, I don't expect that is intentional. Of course, feedback continues to be useful to inform future updates.Anonymous
October 10, 2013
thanks for youAnonymous
October 16, 2013
goooodAnonymous
November 14, 2013
In the enterprise world, what is hurting Silverlight is not the technology itself. So far, there is no other technology come even close on meeting complex client/server LOB requirements, such as rich graphics/animation/user interaction/data driven with the ease of a single shared development environment. It is not Win 8.x or even HTML5. (Just research what OS/Browser matrix most enterprises are using and continue to use for the next 10 years.) What is hurting Silverlight is the uncertainty from Microsoft. Microsoft claims support of Silverlight until 2021. But it is not clear what are actually supported. Unlike other standalone software, we need IE to host Silverlight applications. Will Microsoft guarantee all future IE will host Silverlight until 2021? Why not make hosting Silverlight a big differentiator of IE from other browsers? For many people/enterprises, we will continue using IE as long as it supports Silverlight. Why force people who loves your technology to leave you? For all Microsoft needs to do is to assure us Silverlight will be supported in all future IE/update/IDE at least until 2021 and will be continuously supported if it is still demanded by the industry. We can even live without Silverlight 6. But why not give it some time and let the market decide, with not much effort from Microsoft?Anonymous
November 16, 2013
Code Lens is cool, too bad for me it's not available for C++ code. I'd love to be able to see changeset info for my code.Anonymous
November 16, 2013
Can I speak Chinese?这个很好，很期待。呵呵Anonymous
November 22, 2013
下载Anonymous
December 02, 2013
The comment has been removedAnonymous
December 09, 2013
Unrelated but if your VS IDE's are as unusable and unintuitive as your IE11 IDE then come back later. Unless I'm told otherwise how do you move the way-too-large menubar to the top of the IDE frame? Now I get to unpin which removes me completely from the page content or have 50% of my page obscured by an oversized window. Thanks.Anonymous
January 18, 2014
СпасибоAnonymous
January 18, 2014
free is a good ideaAnonymous
March 06, 2014
me encantoAnonymous
May 01, 2014
Very Good!Anonymous
May 22, 2014
it nice！I like it