CASE Studio 2 v 2.23.1 + Crack Keygen/Serial Date added: Jan 2016 ScreenShot Review this Software Name * Email * Website Comment You may use these HTML tags and attributes: • ODOWNLOADX News • June 18 We have fixed our email. We can now recieve email flawlessly. Email us at [email protected] • Jan 28 OdownloadX changed it's design and layout. Case Studio 2 Full License Cracked. Breaking Celeb News, Entertainment News, and Celebrity Gossip. Translate to English > Translate to English > Translate to English. Free Silhouette Studio Cracked Easter Egg Design. The cracked egg shape is part of the newly released Crafters Bundle from The Hungry Jpeg. If you think this one's cute you should see the rest of the bundle.which is practically free at just $12 for all of the designs (and commercial licenses)! Hope you guys liked it. • Featured Softwares for this Week • • • • • • • • • • • • • • • • •. We’ve released an update to Visual Studio 2017 and you can it and start using it today. In this update, which will show up in Help/About as 15.1 (26403.0), we’ve added support for the Windows 10 Creators Update SDK, added support in Xamarin Workbooks for C# 7, and updated the Redgate Data Tools. There is also a set of performance improvements you can read about in Bertan’s post,. For a more complete list of features and changes for this update, please read our. Windows 10 Creators Update The Universal Windows Platform Tools have been updated to add support for the upcoming. Along with the inclusion of the new Windows 10 Creators Update SDK, we made several improvements, such as an updated, support for UWP projects targeting the Creators Update, XAML IntelliSense warnings for types and properties that are not available on all Windows versions, support for creation of install packages, as well as creation of. To get started building Windows apps with the Creators Update SDK, read the instructions at this. Visual Studio Tools for Xamarin Xamarin Workbooks provides a blend of documentation and code that is perfect for experimentation, learning, and creating guides. In this update, we’ve added support for C# 7 with Roslyn 2.0. So go ahead and try the newest features available in C# 7 by exploring with a. We’ve also improved Xamarin’s memory usage and reduced our disk space footprint so that Xamarin.iOS and Xamarin.Android tools are more lightweight and efficient. Redgate Data Tools Visual Studio 2017 includes the Redgate Data Tools to help you extend DevOps processes to SQL Server databases. SQL Prompt Core is available in the Enterprise edition of Visual Studio 2017 and improves your productivity with advanced IntelliSense-style SQL code completion. With this update to Visual Studio, code completion now works with queries opened outside of the SQL Server Object Explorer. We’ve also added a new link to our SQL Prompt Help menu so you can share your feedback directly with Redgate. ReadyRoll Core is also available in the Enterprise edition of Visual Studio 2017 and is a migrations-first database development and deployment tool inside Visual Studio, allowing you to extend DevOps processes to your SQL Server and Azure SQL databases. With this update, we’ve added support for Azure SQL Database temporal tables. To our customers using Visual Studio Team Foundation Server (TFS) / Visual Studio Team Services (VSTS) Build and Release, we’ve released an update to the with improved messages and formatted, color-coded TSQL for deployment scripts, which makes it easier for you to manage and deploy database changes. For more information about Redgate Data Tools, visit. Share Your Feedback With Us As always, we welcome your thoughts and concerns. For issues, let us know via the tool in Visual Studio. You’ll be able to track your issues in the where you can ask questions and find answers. For suggestions, share with us through. John Montgomery, Director of Program Management, Visual Studio John is responsible for product design and customer success for all of Visual Studio, C++, C#, VB, JavaScript, and.NET. John has been at Microsoft for 17 years, working in developer technologies the whole time. I think Microsoft and specifically, Visual Studio, is always learning and, frankly, figuring out how the heck to interact with you. Some of our users prefer to not hear about the engineering limitations, business considerations or other customer issues that are currently taking priority. Some prefer not to hear about the new, innovative things we’ve built because they’d prefer to maintain consistency with the Visual Studio product they are used to. Some prefer us to stop talking entirely. I prefer to err on the side of positivity because the vast majority of our customers respond well to that. I, and the people I work with at Microsoft, do care about what you need to build the best applications, technologies, or services. I chose to work for Microsoft because I believe our developer tools can help you build the next game changer. My positivity comes from that ?. I cannot “like” / +1 this enough! ? Very well said! I appreciate the VS, VSTS, and TFS team’s new approach toward engaging its users and rapidly iterating to make improvements. Of course not everything will ship perfectly right away, but the responsiveness if much appreciated. As an enterprise consumer (and administrator) of VS, I’m still trying to figure out the new cadence and how to effectively get new version updates out to our internal company user base appropriately. We are learning together so the more I can collaborate with Microsoft, get fast feedback, and iterate, the better the result will be on both sides. I feel like an explanation of how the testing policy changed into the “programmers do their own tests” and dogfooding system was expanded might explain this. This is a change from a few years ago, however I do not believe that the product releases have been fast enough for people to take much notice until said processes affected the products they were working on. And smaller products are probably fixed so fast you wouldn’t see it happening, but a larger product This happened in 2014, meaning that VS 2015 had half of its cycle in the old testing, probably, and half in the new phase, where QA department literally doesn’t exist. They are relying on feedback so these negative comments are actually the desired/expected process. Where exactly is the problem? Exactly the problem is the bad quality of the RTM/RTW product. Never in my life see a finished product with that cuantity of bugs, errors, problems, issues, etc. Is not a stable or finished product. Also, there a parts of the product to be available in May or later. Is not a finished product. Visual Studio was not released when it was finished, but for marketing reasons, it was released on the anniversary date of Visual Studio, what they had developed, regardless of whether it was finished or not, regardless of whether it works or not. The important thing was to meet the anniversary date to match the launch. Marketing questions are more important today than technical issues. We completely hear the frustration here. One of our biggest challenges right now is the ability to test using “real” customer scenarios. A lot of our testing is a combination of unit testing, build testing and dogfooding based on Microsoft development teams using early builds. The problem here is that there are many independent developers, small/medium/large development teams and enterprises that have very unique development stacks. When you report an issue, it gives us a glimpse into what gaps and cracks exist. We patch them and investigate how we can test to prevent similar issues in the future. Very much a learning process! I promise that the technical challenges are top priority for us. Most of my conversations just today have been with our engineering team to discuss how we can address feedback faster and more efficiently. We’re learning and appreciate your patience! “VS2017 is a huge product and bugs are to be expected.” Yes. I’m a dev for more than 3 decades. Bugs are to be expected. Release early to get early feedback. But things like the initial VS2017 release with a broken on-premise TFS client, making it impossible to use it at all. Yes, **it happens, but how does it come such a thing makes it into an official release? For a paid and not cheap developer product? They release previews to gather feedback with the feedback function broken? Again: **it happens, but please The are like giving a Car to the Client to test if he likes it, but oh sorry, the motor isn’t starting at all, thanks for your valuable feedback Please stop treating us devs teh same as your average Excel user struggling with his macros. This is also while you get those angry reactions below. Understandable, but of course completely inappropriate. Hi Nicole I really appreciate your efforts to communicate, and I’m not in a position to tell you how to do your job, but the following things would make us (or alt least me) to feal taken more serious: 1) Do not try to take discussions online by providing your mail address. We others would like to here the arguments. And weather its true or not (I don’t believe its true), it makes the impression you try to hide something. 2) Be careful with answering questions with polished PR statements not answering the question. We Devs have a very good antennas for such things. Even if you mean it honest, it harms your credibility, because it makes you sound like an average PR drone. 3) Do not ask devs to open bugs already filed, do not ask devs to mail you details about bugs already provided in your bugtracking. Weather its true or not, it makes the impression that your are not really using our bug filings, or why else would you harm your own processes by bypassing the official tool with mail requests? 4) MSFT really has to improve a lot in showing action in Uservoice. There are many popular request not getting any attention for severeal years. Make your decision on what user requests are really turned into features transparent. Its obviously not the number of votes And there are promises to improve Uservoice since years. But never any progress. 5) If you cancel promised features, as the backport of the new.Net core tooling to VS2015, communicate it transparent. Don’t think you can get away with just not mentioning it anymore. Users will ask in the comments and will not feel taken serious. 6) Make sure your communication here about upcoming feature matches your public roadmap. We don’t feel taken serious if MSFT officials promise features for the “next version or the version after”, but not seeing those features on any road map. 7) Be honest. Its very obvious VS2017 was released because of the anniversary date, not because it was ready. Stop with “Oh sorry to here you have problems, please write me at”. We all know that you know that it was released with a lot of broken things as on-prem TFS client or JavaScript InteliSense. Because you had to, It was decided way above you. We are devs, we know the game. There is no offense intended, and “you” does not mean you personally. Wow, excellent list. Especially with asking us to take things offline. This seems very much a distraction/tactic to get us to shut up. ? This has happened to me personally with the UWP group a few times and nothing has changed over there, leading me to give up on them entirely and spend more of my time here in the VS/MSDN/.NET realm so I can hassle you all. ? That said, I think the energy/vibe/engagement is much much much better than UWP and should be what MSFT strives to achieve. I also think Joerg’s list is fantastic. As I have shared a great many times, your great team there needs (as in 100% necessity) to throw down some serious cycles and innovation towards developer engagement. This blog is set in 2005 and is a terrible (and embarrassing) medium. You’re a software giant, and how you engage your paying customers with the tools provide them says everything about you and how you really care/feel about those customers. WE CAN DO BETTER!! I KNOW WE CAN!!! Sadly, with [most] everyone having high-speed internet connections, quality control and testing has gone out the window and is now replaced with the mentality of ‘well we can fix it later’. This is not just the case at Microsoft, but game companies and such as well. The quality of everything has become pretty poor due to the ability to have things auto-update or notify of updates etc. So developers anymore seem to become less caring and just toss things together. The various feedback sites from Microsoft / Visual Studio that have so many upvoted and repeated reports that are STILL not fixed are a prime example of how much they do not care about people testing their software and only fix what they feel like fixing as well. There are so many text editor bugs in the C++ editor of VS that have been around since VS2005 and newer, none of which are still fixed in 2017. (All of which have been reported countless times on their feedback tools/sites.). Hi Mike and Mike-EEE, I do apologize that you feel your voices have not been heard. I promise that we’re always working to improve and if you do have any suggestions or issues, the best place for our engineering teams to hear that feedback is through UserVoice and our Report A Problem. Blog comments tend to be very limiting in the type of information we can share with each other (downloadable files, log dumps, source code snippets, etc) and the feedback tools are specifically built so that you have a channel to our engineering team. Though if you have specific questions about this update to Visual Studio 2017, please ask here. We do miss things sometimes and asking for that information might help out a fellow developer! If you have any additional concerns, feel free to email me at and I’ll do my best to help. Hello,.NET Core project support for F# in Visual Studio 2017 was scoped out for the initial release of VS 2017, but is currently being worked on and is on track for a forthcoming VS 2017 release. You can track the progress here: We’re aware of the pain in being unable to load F#.NET Core projects in VS 2017, and we’re working very hard to make sure it’s in a good place very soon. The entire effort is open-source, so you can track precisely what’s happening right now if you’re interested. Meanwhile, you can use F# today on.NET Core without Visual Studio today! If that interests you, there are multiple resources for learning how to build things like web services. Much of the F# open source ecosystem is already using.NET Core today. It’s easiest to get started with the.NET CLI and the Ionide plugin in Visual Studio Code. Soon this year, you’ll be able to use those projects in Visual Studio 2017 as well. Hopefully this is helpful! It’s disappointing how little support MS is putting behind F# generally. Good tooling in VS and support from Microsoft (eg. Having it as part of the default install, promoting it on the welcome page, not hiding the templates under “Other Languages”) is key to having any sort of traction outside of early adopters. Even looking at the blurb under the article we can see it’s not considered a first class language on.Net: “John is responsible for product design and customer success for all of Visual Studio, C++, C#, VB, JavaScript, and.NET.”. F# templates being under “Other Languages” comes from the configuration profile you selected when you installed Visual Studio. If you select General then all languages get listed out at the top level. You can change it by going to Tools -> Import and Export Settings and then Reset All Settings. Step through the wizard and select General when asked for the settings collection. Note that this will obviously reset all your settings. I don’t know of a way to change that option without resetting all settings. As an individual developer, I like getting frequent VS updates. However, as a member of a team, and somebody responsible for build automation, I’m very concerned about this new direction. It’s critical that everybody on the team and the build servers all have **exactly** the same tools. It was reasonable to enforce this when we only had to deal with an RTM and small number of Service Pack/Update releases. It’s not reasonable with weekly or even monthly updates. There’s also an issue of being able to re-create the **exact** VS environment used to build a released product. We have legal/contractual obligations to support some code for years after we ship it — the only way to do that is with the original tools. It’s fair feedback — and feedback we’ve gotten before. When confronted with the situation, the customers I’ve spoken to seem to be disabling notifications of updates and planning to do a periodic roll-out in their orgs after some smoke-testing. A lot of the larger organizations have a pretty notable process that software updates go through — security validation, compatibility validation, open source policy compliance validation — anyway, and they pick up VS updates at best quarterly and more often twice a year, then do a roll-out. There is an easy reason to post anonymous or – as I do – just using my first name: When reporting problems, I frequently have to provide technical background about our project info to MSFT to allow investigation. Provoking my not so common last name, everyone could google me and would know my employer in seconds. I’m not allowed to do that, as you can imagine. Or if I would, I would have to have every post prechecked by some corp legal teams not having clue of what I’m writing about. Once MSFT support even asked my if I could send them or VS Solution for investigation. Of course I understand this wish from a technical point, but this is completely disconnected form any corp reality: Until I would have clearance to do so, if at all, MSFT would be releasing VS2019. @Nicole Bruck, you are full of BS, do you know that? Your PR style replies are vomit inducing. Why didn’t you reply the guy, @Express user that the four replies are not caused by your (MS) policies but because the V(ery)S(low) is so buggy that it needs four patches in first month after initial release? Why did you give him this c**p: “Hello Express user, that’s a great question! In Visual Studio 2017, we want to make sure you always have the latest and greatest version of our tools. We’re going to be speeding up our update schedule and making smaller changes so that you can get the fixes you need faster! ” Unbelievable. Artur, please cut out the personal attacks. It’s not necessary to make your point. We’ve switched to delivering faster releases, as Nicole notes, because we now have the ability to build and deliver incremental updates that are faster to install. Rather than sitting on bugfixes and feature improvements for several months and delivering a larger update, we want to turn around updates more quickly. That also means that a new user installing for the first time today will get all the fixes from day one, of course. For what it’s worth, this is not unique to Visual Studio – many mobile apps update every week, there are new updates for many Linux distributions on a daily basis, and of course Visual Studio Code updates on a similar cadence. Best wishes, Tim Sneath| Visual Studio Team. Tim, your last reply to me is bit unclear. Could you please clarify it then. Are you saying that from now on we will be getting monthly updates to visual studio (be it one or more per month is not really important)? Because in your first reply to me you’ve said: “We’ve switched to delivering faster releases[]” and now in the last reply you are saying something rather different which is: “we have the ability to ship more rapidly and you can expect to see us taking advantage of that ability when we have new features and important bug fixes.” Now Tim, this is very different to the first statement. To have ability to do something and to actually do something are two very different things. Your first reply would suggest that indeed you’ve switched to fast deliveries, and your second reply only suggest that you have the ability to do so and you may (or not) take advantage of it. I’d really like you to answer to the question: Are you saying that from now on we will be getting monthly updates to visual studio? Because if not then, I’m sorry to say, those four updates so far only meant that V(ery)S(low) was released so buggy that you simply had to do something rather very unusual (four patches in a month) and now you are simply trying to smooth things out by saying that other are doing it all the time. Really would like to get to the bottom of this. Hi Artur, my apologies for not responding immediately. Our updates will be coming more frequently and you can expect them to be at least once per month. It’s difficult for us to predict exactly because one thing we’re learning is that we need to find a balance between getting bug fixes to the customers quickly and properly testing/vetting new features with Visual Studio 2017 Preview. It’ll take us some time to find the balance of shipping updates but you can expect them to be significantly more frequent and less disruptive (especially since you can use Visual Studio 2017 side-by-side with Visual Studio 2017 Preview). Thank you for the question and please let us know if you have any more! How do we report a problem when VS 2017 wont start, repair, or uninstall/reinstall? Run – “The setup for this installation of Visual Studio is not complete” Repair – “Setup Operation Failed” Error: Failed to get installed product. [installerId: SetupEngine, installationPath: C: Program Files (x86) Microsoft Visual Studio 2017 Professional, withUpdatePackages: false, error: DependencyGraphConstructionException at Conflicting dependencies for package Microsoft.CodeAnalysis.VisualStudio.Setup Uninstall – “Setup Operation Failed” Error: No Log. Hi MgSm88, I completely understand your concerns and I assure you that our engineering team is working extremely hard at how we guarantee quality while still keeping pace with the new technologies and developer resources. If you haven’t see Daniel’s earlier post,, we now have Visual Studio 2017 Preview for customers who can take a bit more risk in return for trying out new features early and getting fixes much faster. We’ll never be able to promise perfect updates but we will always try our best! If you have any issues at all, I urge you to Report a Problem: so that our engineering teams can investigate quickly. If you bundle 3rd party Visual Studio extensions with the official VS setup, they should have to follow strict requirements: – They must follow the Visual Studio design. The red gate tools in your screen shots here have a completely different visual design that does not integrate well into the VS design. – They must not show any advertisements. VS is not a cheap shareware software. We paid high licensing fees, so I don’t want to see any advertisements like the big “upgrade” button in your screenshot above. Hi Mathias, thanks for the feedback. For what it’s worth, the Redgate tools we’re integrating into Visual Studio aren’t trial or shareware editions – they’re the real deal. We know there are raving fans of ReadyRoll in particular, because of the way it integrates the database into the whole DevOps workflow. So we struck an agreement with Redgate to partner on integrating these capabilities more deeply into Visual Studio. These tools are not available outside of Visual Studio outside of the paid Redgate product. But we do take your feedback onboard: we don’t want this to feel like an ad or trialware. We’re certainly sensitive to that, and we’ll keep working with Redgate to tune the user interface accordingly and to make it feel more integrated with the core product. Thanks again, Tim. Making the WinForms high DPI improvements depend on compilation against.NET 4.7 is a bad move * we need to abandon Windows 7 support by compiling against.NET 4.7 (only available on Win10-RS2 if I understood it right?) * we need to wait until all our WinForms third party components provide a non-backwards-compatible 4.7-only build (if ever!) This will delay adoption of better high DPI support for years. I hope this will be fixed in future updates, having a dependency on everything being compiled against.NET 4.7 is a showstopper since we have a lot of older third party components (some of them didn’t even switch to.NET 4.0 yet because they didn’t want to drop.NET 2.0/3.5 support and running.NET 2.0 code on.NET 4.0 was working just fine). Forgive me while I continue to hold on diligently to my VS2015 development experience until I read a blog post that isn’t overwhelmingly saturated with comments expressing poor reviews/remarks of VS2017. ? I did notice that the problem count went from nearly 10,000 (!!!) to ~5k overnight. From the sounds of the update here, it doesn’t seem that it fixed that many issues. A comment here suggests that those problems are still in fact there, just removed from the community board? That seems suspect and would be great to get a comment from the VS team on this. Excuse me, I meant “excellent, mature, reliable, and tested VS2015 development experience.” It’s so great that maybe the best path forward would have been to (carefully ? ) update the components there instead of/in addition to going with a whole new IDE with so much churn (not to mention, released sooooooo quickly). I also have about 30 extensions installed along with ReSharper Ultimate, which also introduces their own variables and churn. And despite all that, they all currently work together harmoniously right now in a perfect sweet spot of development paradise. Hi Mike, I suspect what you’re seeing is that we bulk-closed a bunch of issues customers had opened against the release candidate that also had either low vote counts or that we triaged and found that we couldn’t reproduce. As you’ve pointed out, we get a lot of issues opened. A lot of them get voted up, have good repros or stack traces or performance dumps, and we’re able to fix them. A lot of them don’t have a repro, and sometimes when reach out to the person who opened the issue we don’t hear back, so we have to close the issue. I’d love it if you’d give VS 2017 a try, but I also hear from a lot of folks that they want to give it more time, which makes sense too. Especially if you’re running with a lot of extensions, I suspect some of them aren’t updated for VS 2017, so you’d probably find something missing. I am curious, though, which extensions you’re using. Coooooool the legendary John Montgomery. ? Thank you for your explanation and taking the time to chat with us commoners. Yeah, that problem count is a double-edged sword, especially when a new product is launched. I’ll be honest and say that when it was reaching 10k it had me scooting towards the exit to check out Project Rider. ? It’s very helpful though. Personally, I’d rather see it in the 1k range max before it would gain my confidence in downloading. This is especially so when you contrast it to Team Services/TFS where problems are in the 100 range (?!). In any case, here is my list of extensions, courtesy of Export Extensions, a super duper handy extension. Thanks, Mike. To your point about the number of issues VS carries, it is a lot. We have a lot of monthly active users (millions) and they give us a lot of feedback. Many/most are duplicates — we’re still working on improving the developercommunity.visualstudio.com to make it easier for customers to know before they open a duplicate, but the heuristics are tough. We also have a lot of issues that resemble, “VS is slow” or “VS crashes” that get voted up and we need to split into their component sub-issues. At some point, we should write a blog post on the systems we’ve evolved to link customer feedback into our bug tracking system, crash-reporting system, and performance-reporting system. Thanks for sharing your list of extensions. I’m seeing a lot of familiar ones. I agree about managing extensions, by the way — I love them and generally run between three and ten including the Productivity Power Tools, a spell checker, and anything Mads Kristensen wrote. We’ve talked about various systems for flagging extensions as “ready” for a particular release but mostly have focused our energy on helping extension authors move forward. Our community is generally excellent at keeping pace with changes in VS, but it’s work for them and for us — our VS partners get early access to major builds and generally have a pretty direct line to the engineering team. For VS 2017, we had several hundred at the time we had our general availability, but there are many more that are still updating (or that don’t need to update because VS added the capability. Unfortunately I’m too polite to write what a “nice” release VS2017 has been so far (hint: ?). Ofc the newest update broke my install yet again. Back to deleting%LocalAppData% Microsoft VisualStudio 15.0_f4938f75 privateregistry.bin and resetting my settings for the umpteenth time, so I can start VS again maybe for a few days. Maybe start to hire some QA guys who actually work and test with non admin rights (another hint: VS fails miserably on Win7 without admin rights*)?! Mind boggling that no one ever even just started VS on Win7 * quote from MSFT: “The root cause of this bug is a limitation in Windows 7 when creating a private registry file if the file was created as Normal user. We have code in VS that set the correct permissions when VS is run as Admin user, and the permissions will work for Normal user as well. So the work-around above should ensure the permission is always correct.”. I’m sure someone has groused about this before (I refuse to google it), but it would be preferred if SQL Prompt Core was included in VS Pro rather than SQL Search since no one on God’s green earth uses SQL Search. Us enterprise devs don’t automatically get MSDN Ent licenses any more, just MSDN Pro. My suggestion: VS Community – SQL Search. Perhaps hobbyists will find value in this. VS Pro – SQL Prompt Core and the invaluable SQL Search. VS Ent – SQL Prompt Pro, Ready Roll, Sql Compare Core, etc. I encourage a crushing distribution of extras for Ent. Hi Anonymous, I urge you to add your voice to the conversations on our UserVoice: where our engineering teams consider the indication of interest of our customers. Please keep your feedback respectful and considerate here. We very much want to hear your thoughts but comments such as, “What is wrong with you?” are hurtful and unnecessary. Tim was explaining that we usually consider DevOps and more advanced features for our Enterprise edition since it usually entails a significant amount of development and resources for development teams to utilize (which tends to be enterprise developers). We do consider our Professional offering important and we’d like to understand more about what you expect in terms of support. UserVoice is a great platform for that! I look forward to hearing your thoughts there. I get your point, but SQL Prompt is good with or without DevOps. Buy Redgate already. ? Anyway, enough complaining. The RedGate stuff at go-live was pure added value. By the way, 1000 thanks for free VS Community and free SQL Server Dev Edition and free stand-alone SSMS. Fantastic, regardless of updates that may or may not be buggy. You would think that folks don’t remember having to buy VS like I had to buy VS 6 back in the 90s. And they don’t remember having to dev against MSDE. They don’t know what MSDE is. Am I gesturing with my cane right now? – thanks for the update, keep up the good work with faster releases, sure eggs will breaks – despite lots of hard work by engineering, things fails just as in the go’ old days – more internal testing on Your side needs to be carried out, some differently by incorporation VSIX, NuGet etc. Outsider feedback possibilities has to improve: 1. Effort is required to get disgruntled Visual Studio users come together – feedback by “tiny” edit textboxes is awkward, could it be possible to use web forms? Uservoice, Connect, vscollect and known MS channels – are too limited for communicating real issues with necessary and sufficient details – very good move with the built-in reporting facility, but needs extra work to benefit all of us – vscollect could be automated more, VS telemetry should not burden developers machines 3. Nice that version numbers are being explicit increased/counted, file naming could also be improved (vs_community_ver_build.exe), instead of age-old generic names. The new VS marketplace is a good step forward, but still time consuming for installing multiple VSIX, Nugets etc. Deferred web download with multi install could be an improvement. “Extensions and Updates” is annoying with constant slow enumeration of the same information, cached lists could easily improve matters. For local VS installation, it would be nice to have a reporting tool for querying a csv list of globally installed VSIX, Nugets. All VSIX could or should be divided into 3.4 groups (green, yellow, red) 7. Nuget packages also to be grouped 8. Current classification/tags are lacking ver_build stability/compatibility/co-existence tags 9. A Visual Studio update should be released together with a status report (file) and published on aka.ms/vs-stat-vsix, as a start a small set of (telemetry for commonly used) VSIX & Nuget packages (Ok/failed, low performant), this would also facilitate the VS community to report whether user installed VSIX, Nuget pacakges works properly with a new VS update, could be a good case where a extended vscollect.exe were used more often. VSIX/Nuget represent a major area for improvement, the constant change of VSIX interface has added to VS IDE’s technical debt. A combined VSIX, Nuget & VS IDE testing, internal VS IDE tests does probably not include a sufficient number of VSIX, Nuget packages before a VS IDE update released? Installation of VSIX and Nuget should be moved to the new VS Installer – this could be easier to implement, outside the IDE, also VS users would have a independent choice to sort things out for a borked VS IDE installation that can’t start, repaired etc. Standalone tools on github such as vsuninstaller, vswhere are also good steps forward, although the tools code needs work in order for outsiders to contribute. The VSSetup powershell cmdlet lacks sane defaultd, it is incomprehensible why all options has to be specified in order to meaningfully use the Powershell cmdlets. Common relevant options should have sane defaults that covers meaningful uses. The documentation in some areas is a sour point, somewhat understandable due to a faster release cadence. Documentation should focus on “recipe” like overview, less text detailed all sorts of options & parameters something that intellisense already provides with fast lookups rolled into the new GotoAll (handy). The documentation in many places centers too much on “how to draw a button”, is a meager source for experienced developers and non-trivial programming issues. Tables with detailed breaking changes are important, should contain pointers to old and new (both ways) – would also be a good filter for the numerous breaking changes, if “before” and “after” had to be documented side by side the same people in favor of breaking changes. Thanks for forwarding the feedback. I have more feedback, initially limited it to 10 items. I have a radical/disruptive change in mind regarding documentation (technical), it is an industry wide problem. Documentation code samples should be written by experienced developers/implementers, each section/chapter should start with a simple overview by detailing common uses, instead wasting real-estate on listing parameters and options that in most cases can be found by improved VS tooling such as the new API browser (.NET 4.7) and migration to docs.microsoft.com. Documentation structurally has not kept up alongside the improved tooling. The main problem is the premise that documentation has been written bottom-up and is text based, diagram and screenshots would help tremendously and too many forwarding links seems to dead or fails. Some new mechanism for “inclusion” similar to “peek” would also help and pop-up forms that would guide the search to relevant area would help much, instead of web page errors. Most developers don’t have the time to get intimate with the inner working of a particular SDK, module or API – in some places it feels just like counting all leaves in a forest. This kind of documentation also get outdated quickly. There has also been a tendency of that the documentation is marketing “speak” of advertise/outline possibilities without focus on what the API functionality actually covers and solve in the current released version. Lack of sufficient quality documentation is part major of technical debt, and also holding back on quicker, wider adaption of new Microsoft technologies. (I also miss the ability to correct typos in the initial feedback/blog comments, sorry for the confusion.). Sajid, I love your breakdown of the “documentation” problem. I agree wholeheartedly. I know it may be frustrating to hear but the best place for us to explore how to provide accurate, relevant, easy to consume documentation is mainly going to grow with our getting started tutorials. Take a look at some of the changes we’ve made recently to Azure docs: and let me know what you think! You can reach me at and share any feedback you have. I, personally, am working on our story for brand new developers using Visual Studio. I would like to experiment and hopefully start to build a great foundation for how we provide information to our customers. I can always use more feedback ?. It is fine that updates are rolled out quickly and frequently but there is one issue that seems to get overlooked. Installing software on your PC is great when you are sat at home with a good Internet connection and no restictions on what you can do but in some/many organisations they bolt down machines to the point of “pain”. Where I am working at the moment the normal developer account has no access to install software but does have access to the Internet. Additionally we get an “elevated” account to install software but that account has no Internet access!! So yes.you guessed it, the wonderfully easy “install updates” from within the VS product are useless to us. So with that in mind can you consider making simple downloadable updates that can be installed offline. Sorry Nicole, but that’s exactly this kind of answer I wrote about in my list above: “we hear this feedback and I promise that we’re working on trying to find the best experience for updates that we can” You have just on “online” installer, the -layout thing is lame joke, as it needs admin right to download files (!!!). The downloader frequently does incomplete downloads resulting in failed installs because of corrupt install file. It does not show any download progress nor speed, so no way to tell if it actually does something or just hangs, what it does from time to time. It struggles with corporate proxies. All of this was reported in detail in user voice. Maybe its time to admit that this installer is completely unusable in enterprise environments, and you know it. So what about “we didn’t have the time to finish it, we know it does not suit any real life enterprise reality, we will make it better for the *next update*. And stop pretending you need feedback to realize the current installer concept is completely braindead for everyone not sitting in front of plenty of bandwidth and having local admin rights. This insults or intelligence. Sorry to say, no offense. You swore us zero MSI, zero registry installer and you still use tons of them. Look at the AndroidStudio-you can get it as ZIP file, unzip and work. If you have AS folder on non system volume it is immune to system failures,system reinstaling,etc. All sdk,ndk and other tools are also ZIPS grabbed by AS or manually by user and all you need to work is specify a path to them. Make the installer the same way,zero msi, zero registry,zero wierd GUIDs scatterd in registry,etc and all things become easier for you and us. Dont be slave of ancient COM,dont made things more complex than they are, break the wrong way of using com and registry in every aspect if you products! Hi mroz, we hear your frustration and we are working hard on making the best installation experience we can. Do you have any specifics for what you would like to see from your Visual Studio installation experience? We can address the core issues when we understand what is most important to you. It’s very easy to get lost in the technical details and lose sight of why we’re actually making the changes. One of our biggest challenges is that Visual Studio is a very long-term product that has had many changes, refactorings and updates over the last 20 years. I completely agree with keeping it simple and our engineering team is doing their absolute best to solve issues without creating more. It’s difficult and we will always appreciate your patience and consideration. My case: I made a typo creating folders tree where all my dev tools always land and VS and Android Studio were placed by my mistake in wrong named folder. So I renamed folder and was able to run AStudio without any problem,all components are related to AS’s root directory,and there is no any registered paths in registry. With VS there was of course problems it wasn’t able properly run. In registry there was a lot of paths to VS’s components,registered COM components, etc. The only way to make it work was uninstall whole VS and install 12GB again in proper path. Few days later I was forced to made clean install of Windows CU, and the same situation,AS and VS were installed on non-system partition,and AS ran without any problems, VS needed to be installed again. I doubt I will live long enough to deploy VS in XCOPY/unzip way. The problem is how you at MSFT understand “installation”. You understand this as scattering components all over the system: Registry,%VSInstallDir%, inside numerous folders in%appdata% local and roaming, vstelemetry, ProgramData package cache,%programFiles% common files *, serviceshub, and many more. The same time you made visual studio code as zip and it just works, in the same way works AS and Eclipse-unzip and work. In this scenario there is nothing that can go wrong with “installation”-no wierd error with COM components,no wierd errors with MSI installer services that are depend on other countless fragile system components and registry entries. If something doesn’t work in AS or Eclipse it means there are missing file(s) inside root dir or you specify wrong path to sdks,build tools, etc in cleary specified settings file. If something doesn’t work in VS it can by anything-wrong registry entries,wrong services configuration,wrong ACLs in COM servers, wrong regsrv-ed components, missing wierd components in ancient 20years old location (i.e. “common files”). You made it so complex because your installation process still integrate tightly your software with system like 20 yeras before, making almost impossible to separate software from system, while the same time whole world try to do all things totally isolated from system, keeping os barely untouched. That’s why there are containers, docker, flatpack,and so on. Wake up, virtual machines with windows + vs isn’t answer for that trend. Just because it’s their job doesn’t mean they don’t love what they do and don’t care about their users. For example, you can see MS people posting here on weekend, I’m pretty sure they wouldn’t need to do that. Most people posting here are devs themselves, and we all had our share of whiny (and sometimes rude) users. Does it mean we hate our job and stopped caring? So let’s give credit where credit’s due. Sure, the bugs in VS are annoying, bugs always are, but I trust VS team is honesly trying to communicate better with us and solve the issues as fast as possible. Trying to update my offline installation directory using command line “–layout”, using exactly the same command and parameters when I created the offline installation. It is now 33GB, from 20.5GB when VS2017 first released a month ago. I thought it should update what ever was updated and remove older packages! Or are you guys treating binary files of the packages like version control like git or whatever, trying to keep all previous versions of packages to be part of the installation?! You guys should REBASE and not do cumulative update the way you are doing it. It became bloated more than it already is really fast (within a month). I understand keeping some old stuff like.NET 3.5 and such, because, you know, developers still develop using old libraries for backward compatibility. But all old versions that was released last month and was updated, should be removed when updating installation folder. Thanks Thaer – that’s really good feedback. We don’t remove old versions by default because in an enterprise environment where these files are typically stored on a network share, multiple users on different versions will use the same cache to modify or update their install. But you’re right – it would be great to have a feature to trim old versions from the network cache. I’ll log a work item for us to consider. In the meantime, if you’re using –layout in a smaller-scale environment and you just want a slim cache of the latest version, you can of course just point the command at a new directory. Best wishes, Tim Sneath| Visual Studio Team. I genuinely believe people are only bothering to comment if they’ve got something miserable to say. I have noticed VS become more buggy, but I’ve been using VS since Visual Studio 6.0 and I can, as a developer, appreciate the huge mass of history in the codebase. Visual Studio is a behemoth, I have my complaints but overall I’m very much appreciating the more rapid release cycle and quicker patching. Previously we’d get a patch up to a year later, so I’m happy to be getting new features and new fixes just like this. VS Team: I appreciate you’ve inherited a twenty year old beast and you’re doing your best to give us the best, so from me it’s a big thanks. In my opinion, VS2017 Professional is nowhere ready for release. The product should still be in beta. I base my opinion on my personal experiences as well as the sheer number of bugs being reported. Yes, some of it works in certain scenarios, but in the case of.net core projects, most of it doesn’t work. Running up a standard.Net Core web application fails. I have just downloaded the very latest version that claims to have fixed all sorts of fringe issues but the basics don’t even work. What is the point of adding more features on top of a system where the basic standard templates don’t work? Hi Greg, I’m sorry to hear that you’ve been having issues with.NET Core tooling in Visual Studio 2017. I understand your frustration, and I’m sorry we haven’t meet your expectations. The team has been hard at work improving the quality of.NET Core tooling. In the next release, you’ll see less new features and more quality improvements, just as you mentioned. If you are up for it, I’d love to follow up with you by email, or Skype, to see if I can help you with your current issues. You can contact me at sayedha AT Microsoft DOT com. Hi, i have a few questions about this new version of VS: 1) How do updates work? If i will create offline installation, will it have all updates included? 2) How do i create offline installer for only c++ and opengl development? I saw some additional flags to select packages, but it still took so long that i just closed it. It would be nice to be able so see the size of each package so that i would know how long i have to wait. 3) How can i download additional packages if i need to? Do i have to make offline installer again or can i somehow select additional packages on visual studio? Because i dont know just how much i need to download, all these required, recommended and additional packages are a big black hole for me, i dont know if those are downloaded by default and if i will need those. Great to be here again. I had been a serious user of VS since VS6 up till vs 2010. I had been away to blend with the industry requirement of mobile apps therefore I switched to other platform. It’s amazing to discover that VS2017 has the capability to target all devices/OS at once. Last week was my first experience with VS2017 and it’s enticing. I would like to know if the C# has the capability to do most of the advance functionalities available on the native OS. For example, on the Android, is it possible to use C# in calling the Sensors (like proximity sensor, gyro compass etc) available on the android device? Let me first say, that I’m immensly grateful for the CMake integration you introduced for c++ – this was the main reason I insalled VS2017 as soon as it was released and also the new fine-grained installer is a hughe improvement. So thanks for providing real benefit compared to VS2015. However, your release policy is just ridiculous: First you release a so called “release candidate” that is not even feature complete, just to make it for connect2016 and then you released a RTM version that I’d call beta-quality at best which requires one hot patch after another. There seems to be absolutely no connection between the technical maturity of your product and the labels you attach to the respective versions and the release dates seem to be chosen purely based on marketing considerations. So it is not suprising that people – which are mostly SW-Developers themselves – feel like you are trying to hide behind marketing B* instead of having an honest conversation. As a long time VS user, I waited for Update 1 before installing a new VS version. Once I figured out how to use the layout thing and had a working offline folder, installation went fast and smooth for.Net and Native Desktop Dev workloads including MFC/ATL support. Also post install updates went without issues and amazingly fast compared to VS2015 updates. Some smoke testing with existing C++/C# solutions did not bring up issues so far. Did not test C++/CLI yet. In general, I really like VS2017 and the direction its going to, but there clearly was to much of a rush. Hope the team finds some time to consolidate VS and concentrate efforts on stabilization. I really don’t like the rude language some posters display, this does not help anything. But I agree with other posters that calling releases not even feature complete “RTM” and releasing with that level of unfinished or even broken features did VS no favor. Regarding most of us SW developers tend to get angry when facing marketing-speak, no wonder you get those kinds of reactions. Keep up the good work. Multiple users at multiple versions? Lets setup a fare more realistic scenario: How are we supposed to keep around 100 dev seats on the same version? How to push updates to them after testing them? How to use our existing WSUS for this? Could you share how you deploy VS2017 at Microsoft? In a way everyone has exactly the same version, which us not necessarily the latest. I would really appreciate to hear how you do this, because we still struggle to figure out how to first hold back and than push VS 2017 updates to our devs in a ordered manner. @Nicole Bruck [MSFT] Since your blog system will not let me reply directly to your previous question: “Hi Charles, I am sorry that is the impression you’re getting from Visual Studio! I would like to understand how we can fix this. Is there anything in particular that you would like to see us change as we start shipping these updates more frequently?” Since you are obviously determined to take this headlong plunge into a brick wall of reality We need a way that does not require having to purchase and setup one or more new servers, why should we have to pay you to stop flooding us with unwanted updates, to prevent our developers from even being given the option of installing your updates until we test and approve them. Once we have approved them it would be nice to be able to push them out in a batch so we do not have to chase down each developer to be sure they all have the same updates applied. I do not understand why Microsoft is determined to treat their development tools as if they are single-user applications, but you are making life for multiple developer teams near impossible. Don’t be to harsh with Nicole. Her job here is to copy-paste the same marketing BS unter each post complaining about the devastating quality of VS. Its not her fault. The new installer is just a punch in the face of every Enterprise customer. They even dare to close the request for a usable installer by referring to this crap. A 100MB behemoth of Javascript over Electron, just to download and deploy some files and pollute the registry. They just could integrate VS updates with WSUS and we could use existing infrastructure. And they pretend needing feedback for such obvious things. We are really considering to cancel MSDN subscriptions for our devs and switch to individual VS licenses. We pay a lot of money, and all they do is to treat us paying customers as betatesters and really thinking getting away with calling this agile. Just to give an example. The really released a VS reproducible not starting on Win7 without admin rights, except deleting an obscure file loosing all extension. Its fixed now, but obviously they released a VS without starting it a single time on Win7 as a normal user. After browsing github and reading what’s happening there, I think the problem is the two MSFTs fighting: The old evil MSFT represented by the VS and the UWP teams vs. The new cool MSFT represented by the github projects. Old MSFT continues the old habbits of releaseing half baked stuff driven solely by marketing and hiding problems behind PR BS. The cool MSFT has a hard time because they have to keep a community of volunteers happy. What’s hard because old MSFT keeps forcing new MSFT to break promises made to the community. MSFT really has to decide if they want to collaborate open and honest with the community, or continue to take important decisions behind closed doors making all the hard working MSFTies on github looking like idiots. Look at the VisualF# project. Its that important for VS, that old MSFT choose to prefer Phyton support and push out F# to VS 15.3. Having C# not ready would have delayed VS. But yes dear community, F# is a 1st class citizen for VS. Really, trust me. If you honestly think that VS 2017/UWP are old Microsoft ROFL! VS 2017 and its UWP cross device fantasy is the infection that is currently destroying what was once a stable development environment. All their focus is on consumer grade toy apps while the businesses who fed their decades of growth are being kick to the curb and left with obsolete and abandoned technologies, WinForm/WPF anyone, and struggling to maintain critical desktop applications that our companies depend on while Microsoft dreams of skimming 30% profits for store sales and lock in licensing via the cloud. So you are welcome to take your open source toys on github, and run off giggling because you got something free, and I will settle for a well maintained, stable development environment from old Microsoft that lets me do my job assuming Microsoft is still able to create one. The VS 2017 bootstrappers available on will download and install the latest VS 2017 release available whenever they are run. If you download a VS bootstrapper today and run it 6 months from now, it will install the VS 2017 release that is available at that later time, If you create a layout, installing VS from that layout will install the specific version of VS that exists in the layout. Even though a newer version may exist online, you will get the version of VS that is in the layout. If you have a Visual Studio subscription, has “Fixed” versions of VS 2017 bootstrappers. These will install a specific build of VS 2017. For example, if you want 15.1 Go to (login to your subscription). Go to “downloads”, search for “Visual Studio 15.1”. Download a product such as “Visual Studio Enterprise 2017 (version 15.1)” and it will give you a “fixed” bootstrapper. Running it will install that specific 15.1 version of VS. Currently fixed VS 2017 boostrappers for the 15.0 and 15.1 releases are available on my.visualstudio.com. More will be added as newer releases occur. @Mike, I have a Visual Studio subscription and I just looked at the fixed “bootstrappers”. I still have a question though, there are 4 versions of 15.0 and 3 versions of 15.1. Which version will I get when I use these bootstrappers? If I install using the 15.1 bootstrapper today and another 15.1 version is released tomorrow, which version would be installed next week? Versions: April 17, 2017 – version 15.1 (26403.07) April 10, 2017 – version 15.1 (26403.03) April 5, 2017 – version 15.1 (26403.00) March 31, 2017 – version 15.0 (26228.12) March 28, 2017 – version 15.0 (26228.10) March 14, 2017 – version 15.0 (26228.09) March 7, 2017 – version 15.0 (26228.04). I just installed this update and, sad to say, I’ve had to go back to using VS2015 as now I cannot get the%^&$ thing to connect to TFS Online (or whatever it’s called this week). Keeps telling me I am “unauthorized” to access my own repository. I used to be able to click “connect” to get it to bring up the sign-in dialog, but now this refuses to show. So basically unusable. The only reason I can see for using 2017 over 2015 was the new language features anyway. It definitely seems no faster starting up and still crashes ocassionally. Also, this new regular update philosophy may be great for my personal PC at home on a fibre connection, but at work where I am offline, it is a complete non-starter: after mucking around with the /layout thing we have had to adopt a policy of sticking with 2015 on our dev machines as it is all too hard. Just installed Windows 10 Creators Update on a machine with the latest VS 2017 prior to that. One thing I noticed straight away is that every single extension and addon has been removed, even in-house ones. Not a great start for me. Incidently, it also reset all default programs in Windows, and removed Windows Photo Viewer from the list of Photo Defaults (everything was reset to Photos, which I loathe) – had to do a reg hack to get it back. Not done any serious testing yet – just two things that struck me in the first 3 minutes.now to see if me in-house VSIXs will install. Have to agree with most other comments here that VS seems to go down hill fast these days. I keep finding that the things I do need is still not working properly (like getting some decent performance) while new things that I really don’t need is added Just look at this updates, there are no clear instructions on how to download them. I can see no option to download the updated themselves, only to download the entire visual studio again. But according to this page: the last version is: “Release Date: June 9, 2017 – Visual Studio 2017 version 15.2 (26430.13)” but looking at my MSDN, the last version I can find of VS2017 is: “Visual Studio Professional 2017 (version 15.2) (x86 and x64) – (Multiple Languages) Released: 5/10/2017” How can I even get hold of the latest versions? Regards, Patrik Johansson.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |