Programmierung
Programmierung vom 12.12.2018 um 13:00 Uhr | Quelle blogs.bing.com
Today, we are announcing the beta release of Clarity, a web analytics product which enables website developers to understand user behavior at scale.
Web developers face many challenges in building compelling and user-friendly websites. Understanding why users struggle, where users run into issues or why they abandon a website is difficult. When making updates to a web experience, A/B experimentation helps developers decide on which way to go. While A/B experiments allow developers to see when their key metrics are moving, the primary drawback is the lack of visibility into why the metrics moved in any given direction. This gap in understanding user behavior led us to build Clarity.
The session replay capability of Clarity allows web developers to view a user's page impression to understand user interactions such as mouse movement, touch gestures, click events and much more. Being able to replay user sessions allows web developers to empathize with users and understand their pain points.
In the Wild West of devices and browsers, the experience you think you are serving and what your users see can be completely different - devices, plugin, proxies and networks can all change and degrade the quality of your experience. These problems are expensive to diagnose and fix.
The first image shows the page of Bing with malware while the second image shows Bing default experience after removal of malware.
Clarity has been used by the Bing UX team at Microsoft to delve into sessions that had negative customer satisfaction and determine what went wrong. In some cases, engineers were able to detect pages that had multiple overlays of advertisements and looked nothing like the expected experience for customers. Looking through the layout anomalies and network request logs that Clarity provides, Bing developers were able to diagnose the cause: malware installed on the end user's machine was hijacking the page and inserting bad content.
With the knowledge of what was causing these negative experiences, Bing engineers were able to design and implement changes which defended the Bing page. By doing so they increased revenue while decreasing page load time - all while giving their customers a significantly improved experience.
Cook with Manali is a food blog and like many other blogs dedicated to cooking, posts begin with a story about the inspiration behind the recipe. Posts have detailed instructions to prepare the meal, high-quality photographs of the finished dish and potentially step by step pictures to help explain the more complicated parts. Near the bottom of the page is a shorthand recipe card summarizing ingredients, instructions and nutritional information. While this long post format enables food bloggers to emotionally connect with their readers and preemptively address any complication in the recipe, some readers would rather get straight to the recipe. 
When the Cook with Manali team started using Clarity, they were able to investigate real user sessions and realized that almost thirty percent of users were abandoning the page before reaching the bottom of these recipe pages, which has important information about the recipe. In many cases, it seemed that users felt they had to scroll too far to get to the recipe that they really cared about and lost patience before making it far enough on the page. The developers realized their strategy was backfiring and creating a bad experience for some of their users, prompting them to add a "Jump to Recipe" button at the top of these pages.
With the new button deployed, the team was able to see traffic going up and abandonment going down. When they dug into these new session replays, they were able to see users utilizing the new button and getting directly to the content they cared about. They saw abandonment for these pages drop down to roughly ten percent, signaling a significant increase in user satisfaction. Interestingly, many users now utilize the "Jump to Recipe" button to then scroll back up to read the larger story afterwards.
Clarity works on any HTML webpage (desktop or mobile) after adding a small piece of JavaScript to the website. This JavaScript code listens to browser events and instruments layout changes, network requests and user interactions. The instrumentation data is then uploaded and stored in the Clarity server running on Microsoft Azure.
Interesting sessions are automatically bubbled up based on Clarity's AI and machine learning capabilities to help web developers review user sessions with abnormal click or scroll behavior, session length, JavaScript errors and more. Web developers can spend less time and gain more insight into their users focusing on the sessions that Clarity marks as most relevant.
Related sessions are a grouping of similar sessions that are recommended based a single session. This feature allows web developers to quickly understand the scope of a specific user behavior and find other occurrences for the same user as well as other users.
Heatmaps provide a view into user behavior at an aggregate level through click/touch and scroll heatmaps. Click/touch heatmap provides distribution of user interactions across a webpage. Scroll heatmaps provide how far users scroll on your webpage.
Sign up at the Clarity website using your Microsoft Account! (In case you don’t have one, you can sign-up here.)
When you create a new project, it will be added to the waitlist. A notification will be sent when your project is approved for onboarding and you can login to Clarity to retrieve the uniquely generated JS code for your project. Once you have added the code to your website, you can use Clarity dashboard to start replaying user sessions and gain insights.
Please reach out to [email protected] if you have any questions.
The Clarity team has also open sourced the JavaScript library which instruments pages to help understand user behavior on websites on GitHub . As Clarity is in active development with continuous improvements, join our community and contribute. Getting started is easy, just visit GitHub and read through our README.
Thank you,
WeiterlesenProgrammierung vom 12.12.2018 um 11:00 Uhr | Quelle microsoft.com
WeiterlesenProgrammierung vom 12.12.2018 um 11:00 Uhr | Quelle microsoft.com
WeiterlesenProgrammierung vom 12.12.2018 um 10:00 Uhr | Quelle microsoft.com
WeiterlesenProgrammierung vom 12.12.2018 um 00:00 Uhr | Quelle blogs.msdn.microsoft.com
The Quantum Architecture and Computation group launched Q#, our quantum computing programming language, a year ago on December 11th, 2017.
Q# 0.1 was the result of a lot of hard work from a small, dedicated team of developers, researchers, and program managers. We had made the decision to build a domain-specific language for quantum computing about six months before we launched, so we were on a very tight schedule. We were lucky to have a great team of people who all pitched in and did what needed to be done so that we could meet our extremely aggressive timetable.
Inside the team, we speculated on what level of interest Q# would attract. We hoped that we might receive a few hundred downloads, but we were blown away when we crossed 1,000 users by about 9 hours after launch. That said, with so many users installing the Quantum Development Kit and trying to write simple programs in it, bugs started popping up. In order to deliver the best experience for our users, we released a patch in January that addressed issues like floating-point literals that were handled incorrectly in certain locales, and allowed the simulator to run on older machines without vector instructions support.
We also addressed portability feature requests in our 0.2 release in February 2018, which saw us move from the .NET Framework to the open-source, cross-platform .NET Core. This allowed us to easily support macOS and Linux as well as Windows for building and running Q# code. We also added support for VS Code on all platforms (the 0.1 release was limited to Visual Studio on Windows). As part of the 0.2 release, we were able to make the majority of our libraries and samples available under an MIT license.
We decided to take advantage of one of our team members’ expertise in organizing coding competitions and run a Q# coding competition to engage non-quantum developers with Q# and quantum computing. After a couple of months of preparation, we ran the Q# Coding Contest in early July. Again, the results exceeded our expectations: 514 participants in the warmup round, and 389 in the actual contest. 100 participants solved all the problems, and a lot of them even asked for more challenging ones!
To help make Q# and quantum computing more accessible to the public, we also launched self-paced programming tutorials: the Quantum Katas. We’re up to 10 katas already, and more are coming!
We started planning the next major release in the spring of 2018, after shipping our 0.2 release: we wanted to rebuild our compiler to work as a language server, to give Q# developers the same interactive error checking and IntelliSense features they’re used to for languages like C# and F#. We knew this would be a huge amount of work and would require a significant re-architecture of the compiler in order to work incrementally. We didn’t want to wait longer to do this work, though, because we wanted to give our users the kind of modern programming environment they’re used to.
We spent the spring and summer re-architecting and rewriting the Q# compiler and shipped the new Q# compiler as our 0.3 release at the end of October.
The 0.3 release also includes a new, open source quantum chemistry library. This library integrates with NWChem, a powerful and popular open source computational chemistry package. The integration is based on the open source Broombridge schema.
What’s next for Q#? No spoilers (yet!).
The last blog post of the calendar, scheduled for December 24th, will look at some of the things we’re considering for Q# in the coming year.
Until then, enjoy the holidays!
Congratulations to everyone who can figure out what the section titles have in common…
 |
Alan Geller, Software Architect, Quantum Software and Applications @ageller Alan Geller is a software architect in the Quantum Architectures and Computation group at Microsoft. He is responsible for the overall software architecture for Q# and the Microsoft Quantum Development Kit, as well as other aspects of the Microsoft Quantum software program. |
WeiterlesenProgrammierung vom 11.12.2018 um 23:30 Uhr | Quelle developer.apple.com
WeiterlesenProgrammierung vom 11.12.2018 um 20:45 Uhr | Quelle channel9.msdn.com
Carlton Gibson, Django Software Fellow and Django maintainer, joins Nina Zakharenko to show how to set up a Python application with Django REST Framework and develop with Visual Studio Code, from installing the Python extensión to using the integrated terminal and debugging. Visual Studio Code is free and open source, and runs on macOS, Linux and Windows.
Python on Azure series:
Follow @nnja Follow @AzureFriday Follow @carltongibson Follow @code
WeiterlesenProgrammierung vom 11.12.2018 um 19:23 Uhr | Quelle blogs.msdn.microsoft.com
Today, we are releasing the December 2018 Security and Quality Rollup.
This security update resolves a vulnerability in Microsoft .NET Framework that could allow remote code execution when Microsoft .NET Framework doesn’t validate input correctly. The attacker who successfully exploits this vulnerability could take control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts that use full user rights. Users whose accounts are configured to have fewer user rights on the system could be less affected than users who are granted administrative user rights.
To exploit the vulnerability, an attacker has to pass specific input to an application that uses susceptible .NET Framework methods.
This security update addresses the vulnerability by correcting how .NET Framework validates input.
To learn more about this vulnerability, see Microsoft Common Vulnerabilities and Exposures CVE-2018-8540.
The Security and Quality Rollup is available via Windows Update, Windows Server Update Services, Microsoft Update Catalog, and Docker.
You can get the update via the Microsoft Update Catalog. For Windows 10, .NET Framework updates are part of the Windows 10 Monthly Rollup.
The following table is for Windows 10 and Windows Server 2016+.
| Product Version | Security and Quality Rollup KB |
|---|---|
| Windows 10 1809 (October 2018 Update) Windows Server 2019 |
Catalog 4470502 |
| .NET Framework 3.5 | 4470502 |
| .NET Framework 4.7.2 | 4470502 |
| Windows 10 1803 (April 2018 Update) | Catalog 4471324 |
| .NET Framework 3.5 | 4471324 |
| .NET Framework 4.7.2 | 4471324 |
| Windows 10 1709 (Fall Creators Update) | Catalog 4471329 |
| .NET Framework 3.5 | 4471329 |
| .NET Framework 4.7.1, 4.7.2 | 4471329 |
| Windows 10 1703 (Creators Update) | Catalog 4471327 |
| .NET Framework 3.5 | 4471327 |
| .NET Framework 4.7, 4.7.1, 4.7.2 | 4471327 |
| Windows 10 1607 (Anniversary Update) Windows Server 2016 |
Catalog 4471321 |
| .NET Framework 3.5 | 4471321 |
| .NET Framework 4.6.2, 4.7, 4.7.1, 4.7.2 | 4471321 |
| Windows 10 1507 | Catalog 4471323 |
| .NET Framework 3.5 | 4471323 |
| .NET Framework 4.6, 4.6.1, 4.6.2 | 4471323 |
The following table is for earlier Windows and Windows Server versions.
| Product Version | Security and Quality Rollup KB | Security Only Update KB |
|---|---|---|
| Windows 8.1 Windows RT 8.1 Windows Server 2012 R2 |
Catalog 4471989 |
Catalog 4471983 |
| .NET Framework 3.5 | 4470630 | 4470602 |
| .NET Framework 4.5.2 | 4470622 | 4470491 |
| .NET Framework 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2 | 4470639 | 4470499 |
| Windows Server 2012 | Catalog 4471988 |
Catalog 4471982 |
| .NET Framework 3.5 | 4470629 | 4470601 |
| .NET Framework 4.5.2 | 4470623 | 4470492 |
| .NET Framework 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2 | 4470638 | 4470498 |
| Windows 7 Windows Server 2008 R2 |
Catalog 4471987 |
Catalog 4471984 |
| .NET Framework 3.5.1 | 4470641 | 4470600 |
| .NET Framework 4.5.2 | 4470637 | 4470493 |
| .NET Framework 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2 | 4470640 | 4470500 |
| Windows Server 2008 | Catalog 4471990 |
Catalog 4471984 |
| .NET Framework 3.5 SP1 | 4471102 | 4470633 |
| .NET Framework 4.5.2 | 4470637 | 4470493 |
| .NET Framework 4.6 | 4470640 | 4470500 |
We are updating the following .NET Framework Docker images for today’s release:
Note: Look at the “Tags” view in each repository to see the updated Docker image tags.
The last few .NET Framework Monthly updates are listed below for your convenience:
WeiterlesenProgrammierung vom 11.12.2018 um 18:30 Uhr | Quelle blogs.windows.com
The OpenSSH client and server are now available as a supported Feature-on-Demand in Windows Server 2019 and Windows 10 1809! The Win32 port of OpenSSH was first included in the Windows 10 Fall Creators Update and Windows Server 1709 as a pre-release feature. In the Windows 10 1803 release, OpenSSH was released as a supported feature on-demand component, but there was not a supported release on Windows Server until now.
OpenSSH is a collection of client/server utilities that enable secure remote login, remote file transfer, and public/private key pair management. OpenSSH is a powerful tool that originated as part of the OpenBSD project and has been used for many years across the BSD, Linux, macOS, and Unix ecosystems. Adding OpenSSH to Windows Server 2019 allows organizations that work across a broad range of operating systems to use a consistent set of tools for remote server administration.
To get the latest information on OpenSSH in Windows, visit the Win32-OpenSSH wiki or Microsoft docs. You will find the most current documentation as well as information about our broader efforts for bringing OpenSSH to Windows.
PowerShell Remoting over SSH is supported with PowerShell Core. While PowerShell Core is dependent on OpenSSH for PowerShell remoting over SSH, OpenSSH is an independent project.
Refer to our Managing OpenSSH Keys document.
The post Windows Server 2019 Includes OpenSSH appeared first on Windows Developer Blog.
WeiterlesenProgrammierung vom 11.12.2018 um 18:30 Uhr | Quelle blog.revolutionanalytics.com
by Mark Niemann-Ross, an author, educator, and writer who teaches about R and Raspberry Pi at LinkedIn Learning
I spend a LOT of time at r-project.org, in particular the sections for documentation and CRAN. But I hadn’t spent much time in the other areas: R Project, R Foundation, and links. When I recently wandered into the foundation area, I discovered something worth talking about: donations to the R Foundation.
I benefit from the work of the R Foundation. They oversee the language, but also encourage a healthy ecosystem. CRAN happens because of them. Updates to R happen because of them. useR! happens because of them. Every day, you and I are the recipients of some part of their time.
The least we can do is show them some appreciation. If you point your web browser at https://www.r-project.org/foundation/donations.html you’ll find a convenient (and surprisingly inexpensive) place to express your appreciation. As an individual, you can send these kind folks twenty-five euros to tell them you’re in favor of what they do.
You can send them more if you like. You can make your twenty-five euros an annual event. If you’re an institution, you can give 250 euros. If you’re really suave and sophisticated, you can give 500 euros. I suspect you could give more, but you may have to warn the R Board of Directors so they aren’t wondering what you’re up to. (kidding!)
Best of all – for your minimum of twenty-five euros you get listed on the R Donors Site. Look close – you’ll even see my name listed amongst the R glitterati.
For those of us in the United States, donations to charitable organizations are tax deductible. However, The R Foundation is not recognized as such in the US. But take heart — The Society of Indian Academics in America has stepped in to provide a method for earmarking donations — and making donations deductible. Look at the very bottom of the foundations donor page for details on how to make this happen.
Calculate the difference in time spent between working with R — and working without R — then divide twenty-five euros by that amount of time. If you’re like me, that becomes a pretty good value. I think it’s well worth the time to make a donation and keep the R Foundation feeling appreciated.
R Project: Membership Fees and Donations
WeiterlesenProgrammierung vom 11.12.2018 um 17:58 Uhr | Quelle channel9.msdn.com
Machine Learning + Natural Language Processing + Source Code = code2vec
Francesc Campoy (@francesc), VP Developer Relations at source{d} joins us to talk about ML-assisted code review (Lookout) and the Public Git Archive. You'll learn how and why source{d} makes uses a dataset based on many GitHub repos available as public datasets to train its models and how "assisted code reviews" apply ML, image processing, and NLP concepts – like word2vec – to code.
Francesc shares his favorite MLonCode moments, why it's made him a better developer, what's coming next, and where you can get started.
:30: What's Machine Learning on Code (#MLonCode)?
1:27: How source{d} builds its datasets
2:13: "How ML on Code's made me a better programmer..."
4:11: What's "assisted code review"?
4:57: Francesc's favorite resources
Learn more about Open Source
Create a free Azure account
Learn more about source{d}:
• Blog: https://blog.sourced.tech/
• Lookout: https://sourced.tech/lookout/
• GitHub: https://github.com/src-d
Get started with #MLonCode
Learn more about word2vec.
WeiterlesenProgrammierung vom 11.12.2018 um 17:30 Uhr | Quelle blogs.msdn.microsoft.com
Last week at Microsoft Connect();, we announced two new benefits to assist cloud migration for our users who have Visual Studio Subscriptions. If you missed the event or want to watch the on-demand trainings, check out the Connect(); event page. If you’re a current Visual Studio subscriber, activate your new benefits to get started right away. To learn more about our developer subscriptions and programs visit the Visual Studio website.
Here are more details on the two new benefits:
Developers need critical insights on their software when migrating to the cloud. With CAST Highlight, Visual Studio Enterprise subscribers can rapidly scan their application source code to identify the cloud readiness of their applications for migration to Microsoft Azure and monitor progress of their app both during and after a migration. Check out this video from CAST to see it in action.
Visual Studio Enterprise subscribers can get a free, full-featured one-month subscription to CAST Highlight for up to five apps per subscriber.
Developers also need solutions that enable quick and easy app migration to the cloud. CloudPilot helps move apps to Microsoft Azure in a few easy steps, including identifying all required changes down to the line of code for successful migration to containers, virtual machines, App Service, Azure SQL, and SQL Managed Instance. See this video from UnifyCloud to learn more about CloudPilot.
Visual Studio Enterprise subscribers are eligible for two 90-day free licenses to the full-featured CloudPilot, while Visual Studio Professional subscribers can take advantage of one 30-day license to scan apps and databases of millions of lines of code in minutes.
Log into the Visual Studio Subscriptions portal at https://my.visualstudio.com today to get your new benefits.
Let us know what you want to see with the Visual Studio Subscriptions by sharing your feedback, suggestions, thoughts, and ideas in the comments below!
 |
Lan Kaim, Director of Product Marketing
Lan is a Director on the Azure marketing team where she is responsible for the developer subscription business. |
WeiterlesenProgrammierung vom 11.12.2018 um 16:47 Uhr | Quelle channel9.msdn.com
This is the last of a three part series where Robert is joined by Chris Woodruff who shows how to build ASP.NET Core Web APIs. In this episode, Chris goes deep into what developers should know when building real-world APIs. This episode expands on the first episode to discuss what best practices developers should think about before, during and after their API project. We look at how and why you should decouple your API from the domain and data logic in your solutions and why we should not use our Entity Framework Core entity models at the API endpoints.
Resources
Episodes:
WeiterlesenProgrammierung vom 11.12.2018 um 15:45 Uhr | Quelle channel9.msdn.com
Are you excited about Azure IoT Edge? Then you are going to love TypeEdge because it simplifies the IoT Edge development down to a simple F5 experience.
Watch how you can now create a complete Azure IoT Edge application from scratch in your favorite development environment, in just a few minutes.
Check out the project on GitHub: https://aka.ms/typeedge
Create a Free Account (Azure): https://aka.ms/aft-iot
WeiterlesenProgrammierung vom 11.12.2018 um 13:00 Uhr | Quelle azure.microsoft.com
We’re excited to officially announce the public preview of the built-in Python images for Azure App Service on Linux, a much requested feature by our customers. Developers can get started today deploying Python Web Apps to the cloud, on a fully-managed environment running on top of the Linux operating system.
This new preview runtime adds to a list of growing stacks supported by Azure App Service on Linux, which includes also Node.js, .NET Core, PHP, Java SE, Tomcat, and Ruby. With the choice of Python 3.7, 3.6 and soon 2.7, developers can get started quickly and deploy Python applications to the cloud, including Django and Flask, and leverage the full suite of features of Azure App Service on Linux. This includes support for deployments via “git push”, and the ability to deploy and debug live applications using Visual Studio Code (our free and open source editor for macOS, Linux, and Windows).
When you use the official images for Python on App Service on Linux, the platform automatically installs the dependencies specified in the requirements.txt file. Additionally, it detects common Flask and Django application structures and hosts them using gunicorn, and includes the necessary modules for connecting to Azure DB for PostgreSQL.
While the underlying infrastructure of Azure App Service on Linux has been generally available (GA) for over a year, at the moment we’re releasing the runtime for Python in public preview, with GA expected in a few months. In addition to using the built-in images, Python developers can deploy their applications using a custom Docker container on Web Apps for Containers.
Carlton Gibson, Django Software Foundation fellow and core maintainer of the Django project, recently joined our developer advocate Nina Zakharenko for a video series on using Python/Django on Visual Studio Code, Azure, and Azure DevOps.
The full walkthrough is available on the Microsoft + Open Source blog.
Let us know your feedback!
WeiterlesenProgrammierung vom 11.12.2018 um 11:00 Uhr | Quelle microsoft.com
WeiterlesenProgrammierung vom 11.12.2018 um 10:00 Uhr | Quelle azure.microsoft.com
We are happy to announce that Azure Monitor for containers is now generally available. Azure Monitor for containers monitors the health and performance of Kubernetes clusters hosted on Azure Kubernetes Service (AKS). Since the launch of the public preview at Build in May 2018, we have seen a lot of excitement from customers. Customers love the fact that you can enable monitoring as soon as you create an AKS cluster and get all the monitoring telemetry in a centralized location in Azure without having to login to containers or rely on other tools. Since the public preview, we have been adding more capabilities and refining the experience based on your feedback. Let’s look at some of the recent changes.
Multi-cluster view – You often have multiple AKS clusters to manage. Wouldn’t it be great to view and manage all your clusters together? The multi-cluster view discovers all AKS clusters across subscriptions, resource group, and workspaces, and provides you a health roll up view. You can even discover clusters that aren’t being monitored and with just few clicks start monitoring them.
Drill down further into AKS cluster with Performance Grid view – To investigate further, you can drill down to performance grid view that shows the health and performance of your nodes, controllers, and containers. From the node view tab, you can easily spot the noisy neighbor issue on the pod and drill further to see the controller it is part of. You can further see the controller limits, request setting, and actual usage to determine if you have configured your controller correctly. You can continue investigating by looking at the Kubernetes event logs associated to that controller.
Live debugging – We all know the importance of verifying that your application is working as expected, especially after you deploy an update. With live logs you get a real time, live stream of your container logs directly in your Azure portal. You can pause the live stream and search within the log file for errors or issues. Unlike the Azure Monitor logs, the live stream data is ephemeral and is meant for real time troubleshooting.
Onboarding – In addition to the Azure portal, we have added more ways for you to automate onboarding Azure Monitor for containers.
For new AKS clusters:
az aks create --resource-group myAKSCluster --name myAKSCluster --node-count 1 --enable-addons monitoring --generate-ssh-keys
For existing AKS clusters:
az aks enable-addons -a monitoring -n MyExistingAKSCluster -g MyExistingAKSClusterRG
You can also enable monitoring for your containers by using Azure Resource Manager (ARM) template. To learn more, please review the detailed instructions for onboarding using Azure CLI and ARM template.
We would like to conclude with some inspiring words from one of our customers, Hafslund, a Nordic power company, with whom we recently published a case study:
“We found it easy to get Azure Monitor up and running for containers. The metrics and charts right out of the Monitor box are perfect to help us quickly tune our clusters and services and resolve technical issues.”
- Ståle Heitmann, CTO, Hafslund Nett AS
To learn more about Azure Monitor for containers, read our documentation, “Azure Monitor for containers overview.” Thank you for your feedback during the public preview and we look forward to your continued support as we add more exciting features and capabilities to Azure Monitor for containers.
WeiterlesenProgrammierung vom 11.12.2018 um 09:30 Uhr | Quelle azure.microsoft.com
Welcome to KubeCon North America 2018, and welcome to Seattle. It’s amazing to get the chance to welcome you to my hometown, and the site of Kubernetes birth. It was barely five years ago that Joe, Craig, and I had the first small ideas and demos that eventually turned into the amazing project and community. I’m honored that all of you over the years have chosen to invest your time, energy, and enthusiasm in Kubernetes, whether this is your first KubeCon or you’ve been here since the first one in San Francisco four years ago, welcome!
For the Azure Kubernetes team, KubeCon is especially exciting. It’s been a busy and fulfilling year, Azure Kubernetes Service (AKS) has been the fastest growing service in the history of Azure Compute, that’s been quite a ride! With KubeCon here, it’s a great chance to meet up with our customers and community collaborators to celebrate all the incredible things.
For the Azure Kubernetes Service, we started with the journey of "how to make Kubernetes easier for our customers." For example, by letting Azure take care of deployment, operations, and management of Kubernetes APIs and leveraging integrated tools, Maersk was able to free their engineers and talents to focus on things that makes the most business impact. Furthermore, by taking advantage of a fully-managed runtime environment provided by AKS, Siemens Healthineers realized shorter release cycles and achieved its desired continuous delivery approach in highly regulated environment.
We're seeing more and more Java customers port their existing Java application stacks to AKS with little or no changes. Xerox, for example, was able to run their Java apps in containers with no code modifications and leveraged Helm chart to automate customer onboarding. As a result, for their DocuShare Flex Content Management platform they were able to reduce the provisioning time from 24 hours to less than 10 minutes, accelerating sales and customer onboarding.
While we’re discussing Azure Kubernetes Service, it’s great to see more and more Azure services bring their strengths to Kubernetes. Here at KubeCon, we’re announcing the general availability (GA) of the Azure Monitor for containers. The Azure Cognitive Services have also announced containerization of their cognitive APIs, allowing users to take advantage of core cognitive technology on-premise, at the edge or wherever your data lives. For the Azure Kubernetes team, it’s been an exceptionally busy month, starting with the announcement, at KubeCon Shanghai, of AKS in Azure’s China region. Just last week in Las Vegas, we announced the public preview of AKS virtual nodes which together with Azure Container Instances (ACI) helps customers realize and take advantage of a serverless container infrastructure.
But honestly, the service that we build is only one (albeit very important) piece of what we work on as a team. Of equal importance is the work that we do in the open source community to work with others to develop novel solutions to our customers problems. With help from the community, like the great folks at the open policy agent framework, we launched an open source policy controller for Kubernetes. This policy agent installs on Kubernetes clusters anywhere and can provide enterprises with assurances that developers will successfully build reliable and compliant systems. We also are announcing the Osiris open source project that enables efficient “scale-to-zero" for Kubernetes containers. This technology can power Functions as a Service, or any programming paradigm where you need rapid scale-up in response to customer traffic.
With Docker, Bitnami, Hashicorp, and others we’ve announced the Cloud Native Application Bundle (CNAB) specification. CNAB is a new distributed application package that combines Helm or other configuration tools with Docker images to provide a complete, self-installing cloud applications. To see what CNAB can do for you, imagine being able to hand out a USB key to KubeCon attendees that could install your complete application. Finally, we’re celebrating the adoption of the Virtual Kubelet project into the CNCF sandbox, as we continue to work with VMWare, AWS, hyper.sh, and others in the community to make nodeless Kubernetes a reality.
At KubeCon Shanghai, I talked about my thoughts on serverless Kubernetes and the evolution of cloud native development. It’s a future driven by our mission of “Kubernetes for Everyone,” this includes reducing the complexity of Kubernetes operations by running your API for you in AKS and developing ‘nodeless’ Kubernetes with virtual nodes. It also means working on tools like Draft, and the Kubernetes extension for Visual Studio Code, which has been installed by nearly 175 thousand people that make Kubernetes a more integrated, easy to use experience.
At KubeCon North America, I’m taking off my forward-looking cap, and instead talking about the development and maintenance of the Java, .NET, TypeScript, and Python clients for Kubernetes. Whether you’re interested in talking about the future of cloud computing, or adding features like port-forwarding to the TypeScript client. I’ll be around the conference all week at the Azure booth and in the hallway track.
When it comes to explaining Kubernetes, one of my favorites is the Children’s Illustrated Guide to Kubernetes. For this KubeCon, I’m incredibly excited to announce that Microsoft is donating the likeness of Phippy, and all of your favorites from the book to the CNCF. To celebrate, we’re sharing a special second episode of the Children’s guide to Kubernetes. You can learn about the core concepts of Kubernetes in a fun way!
Whether you’re joining us in Seattle for KubeCon, or watching the talk streams from afar, we’ve got some great resources to get you started with Kubernetes, including the recently published best practices we’ve gathered from our customers and a webinar I will be sharing on structuring Kubernetes project in production.
Welcome to Seattle!
--brendan
WeiterlesenProgrammierung vom 11.12.2018 um 09:00 Uhr | Quelle azure.microsoft.com
We’re excited to see everyone at Kubecon this week! We’ve been working with our customers to understand how they’re thinking about Kubernetes and what we can do to make it easier for them. Azure Stack unleashes new hybrid capabilities for developing applications. You design, develop, and maintain your applications just like you do with Azure and you can deploy to any of the Azure clouds. Your application’s location becomes a configuration parameter rather than a design constraint.
So how does Azure Stack work with containers exactly? The way that containers and hybrid cloud work together can allow you to solve many problems. You can create a set of apps in containers using the languages you love like NodeJS, Python, Ruby, and many others. You can also take advantage of the wide array of tooling available, including Visual Studio Code. You can deploy your container or set of containers to a mix of environments that meet your user’s requirements. For instance, you can keep your sensitive data local in Azure Stack and access current functionality such as Azure Cognitive Services in global Azure. Or you can develop your apps in global Azure where you developers are and then deploy the containerized apps to a private cloud in Azure Stack that becomes completely disconnected on board a submarine. The possibilities are endless.
Azure Stack allows you to run your containers on-premise in pretty much the same you as you do with global Azure. You can choose the best place for your containers depending on data gravity, data sovereignty, or other business needs. Containers let you use Azure Services from your host running on-premise and lets you take advantage of the secure infrastructure, integrated Role Based access Control, and seamless DevOps tools allowing you to create a single pipeline targeting multiple Azure clouds. Your containers and supporting services are hosted in a secure infrastructure that integrates with your corporate network.
The Kubernetes Marketplace item available in Preview for Azure Stack is consistent with Azure since the template is generated by the Azure Container Service Engine, the resulting cluster will run the same containers as in AKS. It also complies with the Cloud Native Foundation.
Your developers can also use Open Shift Container Platform in Azure Stack. Open Shift provides a consistent container experience across Azure, Azure Stack, bare-metal, Windows, and RHEL. Open Shift brings together Microsoft and Red Hat developer frameworks and partner ecosystems as previously announced in September.
When you take your containers across Azure, Azure Stack, and Azure sovereign clouds, you should also consider that your application architecture likely depends on more than containers. Your application likely depends on numerous resources with different, specific versions. To make it easier to manage this, we recently announced the Cloud Native Application Bundles, a new open source package format specification created in close partnership with Docker and broadly supported by HashiCorp, Bitnami, and more. With Cloud Native Application Bundles, you can manage distributed applications using a single installable file, reliably provision application resources in different environments, and easily manage your application lifecycle without having to use multiple tools.
This week is KubeCon and if you are attending you can see Kubernetes and Azure Stack in action in the Expo Hall. Please drop by our booth #P18 to see great demos of the technologies I mentioned in this post.
I hope you find the information in this post useful! Stay tuned for new topics around developing hybrid applications and feel free to follow me on Twitter.
To learn more about hybrid application development, read the previous post in this series: "What you need to know when writing hybrid applications."
WeiterlesenProgrammierung vom 11.12.2018 um 00:26 Uhr | Quelle blogs.msdn.microsoft.com
If you try to install Build Tools for Visual Studio 2017 into a Windows Server 2019 or newer container image, such as mcr.microsoft.com/windows/servercore:1809 or mcr.microsoft.com/windows/servercore:ltsc2019, the install will quickly terminate without error and without installing anything. This is due, in part, to changes to the Windows Server container image to reduce size and improve startup performance.
To install into Windows Server Core 2019 or newer, please download Visual Studio 2017 version 15.9 or newer, including Visual Studio 2019 Preview 1.
Note: all previous Windows container images are now available in the Microsoft Container Registry (MCR), and all new container images including build 1809 (aka “RS5”) will be available only on MCR. See the Virtualization Blog for more information. However, Build Tools should still only be installed on microsoft/dotnet-framework images available on Docker Hub. See Known issues for containers for more information.
WeiterlesenProgrammierung vom 10.12.2018 um 20:55 Uhr | Quelle channel9.msdn.com
This video introduces the concept of decentralized identity and how blockchain enables hosting these identities in a decentralized fashion. The demo provides a walkthrough of a decentralized identity that is anchored on Ethereum blockchain and is consumed using uPort application.
Additional details and sample code are available on GitHub at https://github.com/Azure-Samples/blockchain
WeiterlesenProgrammierung vom 10.12.2018 um 20:27 Uhr | Quelle blogs.msdn.microsoft.com
Today, we are excited to announce that we are open sourcing XAML Behaviors for WPF.
In the past, we open sourced XAML Behaviors for UWP which has been a great success and the Behaviors NuGet package has been downloaded over 500k times. One of the top community asks has been to support WPF in the same way. XAML Behaviors for WPF now ships as a NuGet package – Microsoft.Xaml.Behaviors.Wpf . This will allow new features and bug fixes to be addressed faster. When a new Behavior or feature is added to the repo, it can be consumed and used almost immediately. Opening to contributions lets the Behaviors platform grow by empowering the community to set the pace and direction. While you can continue to use the Extension SDK, further development will only take place on GitHub and be published in the NuGet package under the new namespace Microsoft.Xaml.Behaviors.
You can install the latest version of WPF XAML Behaviors in both Visual Studio and Blend using the NuGet Package Manager:
From the package manager console:
PM > Install-Package Microsoft.Xaml.Behaviors.Wpf
From Blend Assets pane:
Like UWP, we have made updates to Blend for Visual Studio 2019.Instead of presenting a pre=populated list of Behaviors in the Assets Pane, Blend prompts the user with a link to install the NuGet Package. Clicking this link will download and reference the latest NuGet Package and populate the list with the latest and greatest Behaviors. Note that if this is an existing project which references the old Behaviors SDK, the list will be pre-populated with the Behaviors from the SDK. See below for steps to migrate to the NuGet package.
The NuGet package ships with DLLs under the “Microsoft.Xaml.Behaviors” namespace. Since the APIs for WPF are the same as the original Extension SDK, switching over is as easy as installing the NuGet package and updating the xmlns and the usings. Note that Behaviors are not yet fully supported on .NET Core.
A big thank you to our MVP leaders for dedicating their time and effort in helping guide this project as WPF XAML Behaviors are opened to the community.
Contributions of new and useful Behaviors are welcomed and encouraged. Have feedback, suggestions, or comments? We would love to hear them – please submit an issue on the GitHub page or email us.
Weiterlesen
Nächste 2 Seite | 
Letzte Seite