Creating a windows service itself is a hassle that includes various aspects of it like configuration, install-uninstall, recovery, start mode etc. Managing this settings is either can be achieved manually or by writing bunch of batch/command files that helps in deployment and management of windows services. Recently, I came across an ultimate .Net OSS library that provides control almost
Changes in licensing allows anyone with the basic CAL to get access to features that were available only to premium subscribers.
July 29 is not just the day that Windows 10 starts rolling out. It's the day its new unified app store opens to developers, too.
If there's some piece of data that you find interesting, you don't have to keep asking Visual Studio to display it. Instead, you can keep it around for as long as you want -- even when the code it's part of isn't on the screen.
Container OS comparison | via @codeship
Solomon Hykes’s famous five-minute presentation at PyCon
There are several projects around management, network, storage, logging, monitoring, and more (check out this awesome mind map of the ecosystem).
“Which is the best OS to run containers?” That’s usually followed by “Is
it CoreOS? What about RedHat? I’ve also heard about something called
When we wrapped up the last release of Visual Studio, I wrote a blog post titled: Visual Studio 2013 Diagnostics Investments, which gathered all the links to our blog posts and other content into a single place. It seems fitting to do the same now that VS2015 has RTM’d, and the same intro I wrote last time applies, so I won’t repeat that here. When I think of the Diagnostics Investments we made in this release, I classify them into 4 broad buckets: platform support, addressing customer feedback, catching performance issues early, and historical debugging with IntelliTrace. Platform support Every
time Visual Studio needs to support a new operating system version or platform, the Visual Studio Diagnostics team has to do a bunch of work just to keep things working before even considering adding new capabilities – and we added a bunch! This release was no different, adding support for Windows 10 and the various Windows 10 device types, e.g. desktops, tablets, phones, Xbox, and HoloLens. You can now enjoy the regular awesome Visual Studio debugging and profiling experience for all those devices. The same applies to profiling and debugging .NET Native apps and debugging support for ASP.NET 5. In addition,...(Read whole news on source site)
In this post of the Office 365 Groups for Admins series I will talk about the small but important policies we can apply to Group creation. At the moment there is very little control of the actual Office 365 Group creation in Office 365. And this tends to be one really important aspect of the Unified Groups discussion - can we allow them or not? I do hope that I over the time can update this post with new and improved governance features. Group naming policies One of the few configuration options you have for the Unified Groups is
how they are named when created. You do not configure this from the Groups settings in the Admin portal, where one could expect it to be, but rather under Admin > Exchange > Recipients > Groups. Then click on the ellipsis (…) and Configure group naming policy: The Group Naming Policy consist of two parts; General and Blocked Words. An important thing to remember is that these policies only applies to when an end-user creates a Group in the user interface (web or Outlook 2016), not when an administrator creates them using PowerShell. General Under the General configuration...(Read whole news on source site)
This one is a pretty recent one. A customer complained about high memory usage in RavenDB under moderate usage. That was a cause for concern, since we care a lot about our memory utilization. So we started investigating that, and it turned out that we were wrong, the problem wasn’t with RavenDB, it was with the RavenDB Client Library. The customer had a scenario where 100% of the time, after issuing a small number of requests (less than ten), the client process would be using hundreds of MB, for really no purpose at all. The client already turned off
caching, profiling and pretty much anything else that both they and us could think of. We got a process dump from them and looked at that, and everything seemed to be fine. The size of the heap was good, and there didn’t appear to be any memory being leaked. Our assumption at that point was that there is some sort of native memory leak from their application. To continue the investigation further, NDAs was required, but we managed to go through that and we finally had a small repro that we could look at ourselves. The fact that the...(Read whole news on source site)
Update: As correctly pointed out by Jan in the comments this post should have been numbered 1908 rather than 1909. I’ve corrected the post title, but the URLs are going to remain Information Roslyn and Mono – Miguel de Icaza ReSharper 9.1.2 for Visual Studio 2015 RTM – Jura Gorohovsky Visual Studio 2015 RTM: What’s […]