1,812 karma · joined May 27, 2011
Disclaimer: The keyboard layout is different, and it will take some time to adjust. I think it's worth it, but be forewarned.
Also, hi Phillip! High five!
The logic here is that, despite being lied to by a trusted account manager, they shipped all of their promised products, at very high quality. They have made continued software updates for years, much better than either Kickstarters or other project's I've purchased: https://github.com/keyboardio/
If you follow their updates, they've made many trips to China, despite having a newborn baby and running a new company.
.NET Foundation is an independent organization, with Microsoft as an important member and big contributor, but .NET is owned by the community. I've heard a lot of great ideas for how the .NET Foundation could support projects better, do more for our Meetups (including providing content, support speakers with things like speaker grants, etc.), put on in person events, etc. - but we haven't had a good way for people to make it happen, and the foundation could only do so much. Now, by letting the community guide the foundation through community board seats and bringing on corporate sponsors, we really can scale up so that if someone has a great idea, they can just do it!
1. Start with conversation - it's much better to start with a new issue or a comment on an existing issue, letting the repo owners know that you're interested and want to contribute to a specific issue. They may give you tips, let you know that the issue's already being worked, etc.
2. Docs are a great way to get started. You can go to any of the .NET Core / ASP.NET Core docs on docs.microsoft.com (e.g. https://docs.microsoft.com/en-us/aspnet/core/), click the edit button, make your corrections or contributions in the browser, and submit.
3. Many projects use the up-for-grabs label for issues that are easy for first time contributors, e.g. https://github.com/aspnet/AspNetCore/labels/up-for-grabs (again, start with a comment on these, since some of them are a little old and may no longer be relevant)
4. Don't just think about the big name .NET projects. Membership is open to contributors to any .NET Foundation project, including a lot of projects with small teams that would love some help. Check out the full list here (https://dotnetfoundation.org/projects), or tweet me with hashtag #dotnethelpwanted and I'll rt to help get you matched up.
5. Check out some of the help wanted listings, e.g. https://discoverdot.net/issues/?tab=helpwanted (remember we're looking for .NET Foundation projects for membership)
* Faster
* More secure
* Write plugins in C#
* Use NuGet / .NET libraries in Wordpress
* Best of Wordpress ecosystem + speed / perf / ecosystem benefits of .NET
* Why not?Disclaimer: I don't know if this affects your concerns, but it's at least the right license. Disclaimer 2: I work for Microsoft, but not for MSR, and don't know anything specific about this.
https://blogs.msdn.microsoft.com/webdev/2018/02/27/asp-net-c... https://docs.microsoft.com/en-us/aspnet/core/security/enforc...
As the letsencrypt article points out, you want to start building and testing with HTTPS as early as possible, so this is all wired up as part of creating a new project with ASP.NET Core 2.1.
[disclaimer: on .NET team, Nazgûl]
That specific code sample looks like it was based on the Teleport sample: https://github.com/StationQ/Liquid/blob/master/Samples/Telep...
One of my favorite things about the ASP.NET team is that a lot of them were community leaders - speakers, writers, open source library authors, etc. - before being hired at Microsoft. So it's hard to pick just one or two community leaders on the team, as pretty much everyone regularly speaks at conferences, publishes open source code, blogs, etc. So it's really hard to make a short list! Hopefully this is still useful to someone.
As several others have mentioned, you really should start with Scott Hanselman (https://www.hanselman.com/ and @shanselman). [Disclaimer: he's my boss, but I joined his team because I was a big fan long before either of us worked at Microsoft]
The ASP.NET Weekly Community Standup is a great place to connect both with the team and with the leading members of the developer community. It's at https://live.asp.net/ with Damian Edwards, Scott Hanselman and me. Damian Edwards (https://twitter.com/damianedwards) is the program manager for the ASP.NET team. During the show, I usually share 10ish links to top posts, open source projects, etc. by the community. We feel like the ASP.NET Community is made up of developers both inside and out of Microsoft, so you'll see a mix. The links are usually in the show notes, and we also tweet the links out daily at @aspnet. I'm not going to risk making a list because I don't want to leave anyone off - there are too many for me to even try to pick favorites!
Next, check out the "official" Web Dev blog: https://blogs.msdn.microsoft.com/webdev/. We have a general rule that all posts are signed by actual people, not "the ___ team", so you can see who's working directly on specific topics. You'll definitely see a lot of posts by Jeff Fritz (my team mate), who (in addition to program managing several features) does a ton of work to write up release posts, organize content for conferences, etc.
I think of David Fowler (https://twitter.com/davidfowl) as the "crazy genius" on the team. He and Damian wrote SignalR, he worked on prototyping some of the very early work that became ASP.NET Core (and .NET Core all up), etc. Check out this video to see what I mean: https://channel9.msdn.com/Events/NDC/NDC-Oslo-2017/BRK06
For front end dev, make sure you follow Mads Kristensen (https://twitter.com/mkristensen) and Steve Sanderson (https://twitter.com/StevenSanderson). Mads is a program manager for web developer tools in Visual Studio, and also writes a ton of open source Visual Studio extensions for web developers (https://github.com/madskristensen) and builds things like http://webdevchecklist.com/. Steve is always pushing the boundaries of front end development, both with things like JavaScriptServices (https://github.com/aspnet/JavaScriptServices, now shipping in the Visual Studio 2017 Angular / React project templates) and more recently with Blazor (https://github.com/SteveSanderson/Blazor - .NET code running in the browser via Web Assembly).
You'll also see Glenn Condron (https://twitter.com/condrong) listed on several of the recent Web Dev blog posts. He covers a lot of deep back end tech, including a lot of stuff with ASP.NET Core on Docker.
You can see quick (5-10 minute) interviews with most of those people, as well as a lot of other people on the .NET team, on a show that Maria Naggaga (https://twitter.com/ladynaggaga) and I started up recently called Code Conversations (https://channel9.msdn.com/Shows/Code-Conversations). These are short, code focused interviews you can watch while your code is compiling and hopefully put to work right away.
Finally, please ping me at @jongalloway if I can help connect you with anyone or if you're having trouble finding information, code samples, etc. I'm happy to help!
https://www.howtogeek.com/258518/how-to-use-zsh-or-another-s...
You can look up all the awesome lists here: https://github.com/sindresorhus/awesome
Here's an FAQ: https://github.com/dotnet/standard/blob/master/docs/faq.md Here's a series of short videos from the product team explaining it: https://www.youtube.com/playlist?list=PLRAdsfhKI4OWx321A_pr-...
Short excerpt from the FAQ:
.NET Standard is a specification that represents a set of APIs that all .NET platforms have to implement. This unifies the .NET platforms and prevents future fragmentation. Think of .NET Standard as POSIX for .NET.
Having a standard solves the code sharing problem for .NET developers by bringing all the APIs that you expect and love across the environments that you need: desktop applications, mobile apps & games, and cloud services.
Conceptually, I think of it in terms of browsers and browser standards. The relationship between .NET Standard and the various .NET platforms (.NET Core, .NET Framework, Mono, Xamarin, UWP, etc.) is similar to HTML specifications (e.g. https://www.w3.org/TR/html5/) and individual browsers. Newer HTML features are available on newer browsers, and some browser feature implementation is contextualized (e.g. some web features don't make sense on a mobile phone browser). I know there are rabbit holes to #wellactually on that, so if it doesn't work for you don't worry about it, but as an analogy I've found it helpful.Having a defined feature matrix makes it easier to see which APIs are available for a given platform and version.
(Microsoft employee, .NET team member, Nazgûl)
Disclaimers: Inside the US, Microsoft employee, Nazgûl
[disclaimer: Microsoft employee, .NET Foundation staff]
echo Y | format Z: /FS:NTFS /X /Q
source: https://superuser.com/a/352321Also, on Windows 10 you can use Ubuntu bash and run rm -rf. I've read that it's faster, but haven't tested extensively.
Update: I did a quick test with 100,000 files and the 'del /f/s/q foldername > nul' approach was about 50% faster than 'rm -rf' on my machine.
Here's the latest discussion I saw on it: https://community.ardour.org/node/14616
SignalR for .NET Core is under active development (https://github.com/aspnet/signalr), but a release date hasn't been announced. SignalR brings in things like connection and group management, and the update can take advantage of some of the performance and architectural changes in .NET Core.
[Disclaimer: Microsoft employee, Nazgûl]