I would keep in mind that .NET Core is probably still bleeding edge to the majority of software companies out there. In the Microsoft culture, I'm sure things move at the speed of light. Every 2-3 years platforms change, products move mountains, but so many companies the underlying technology is not the priority, but sales are. This means that most executives could care less if you're running Web Forms or AspNetCore. The companies that stay bleeding edge are doing things right though, and probably have the right application architecture in place to move the platform specific code to the new platforms regularly. Most companies and developers in my experience have not had this luxury. Where I work, I am working on building out this platform for an existing large enterprise application that was written in AspClassic, but it is a huge undertaking.
We tried Visual Studio Live Share few times. I think it is very cool, but Slack and its multiple person screenshare controls (multiple mouse cursors)+audio render it not very viable. The biggest drawback, is most often during a collaboration session, we might need to use other programs outside of Visual Studio, including research in the browser.
Maybe adjust the video title to "Managing User Secrets with Azure Key Vault". From the title I thought this was more generalized and going to cover a few different methods of managing user secret information (web.config, app.config, config encryption for sections, windows data protection api, et cetera). At work, we develop an enterprise intranet application for banks where Azure is not an option, so we have to use other methods of securing information.
The release timeframe for the right-click menu was covered, but I think those who may not have been so intently focused might have missed it because it was very brief, but it will come in a future release is what I gathered.
Good video though. We use Azure for DevTest heavily - using user secrets for some of that might be applicable. I thought I heard him say 3 cents per transaction though? That can get very costly!
To comment on something Robert said: I would say that abstract classes can appear to be the Template Method pattern, but rather can implement the pattern for one of its methods. The Template Method (hence the name) is specific to the fact that you have a particularÂ method that defines an algorithm with parts of the algorithm can be delegated to an implementer/override. Where an abstractÂ class doesn't necessarily define an algorithm in of itself, it defines an objectÂ with state and behavior. Also different from strategy pattern, where it tries to focus on allowing an entire implementation of an algorithm to vary from one implementation to another (quick sort, bubble sort), and does not care about the algorithms structure.
Great video, but I felt that it could have better been described as different from other patterns by focusing on the fact that the pattern is really for a method that defines an algorithm, where abstract classes are just one mechanism for facilitating that.
The series is great, should do more content like this. Developers really need to know this stuff.
I have a question. Does this mean that Visual Studio team will be using this technology when compiling the IDE itself, so that the startup times and performance of Visual Studio can take advantage of these benefits?
Is there any possibility of us getting direction on the future of WPF from someone at Microsoft? Should we still be investing in it? Amazing technology (and by far my favorite), but some concerns as things like HTML5/MVC get all the buzz, and we don't hear much about WPF any more.
@Flynn0r I agree to an extent here, the main thing I find really frustrating is differentiating file types in the solution explorer, and I know they are trying to clean up and erradicate toolbar commands to some extent, but some of them are useful and its hard there too.
Other than that I completely agree, VS11 is amazing and I'm already developing some production projects with it.