We have launched the BizTalk Server 2016 Developer image on MSDN. You can download this by going into our MSDN subscriber download site.

BizTalk Server 2016 Developer is a free licensed product that can be used in testing. It does not require an MSDN subscription, however only MSDN Subscription holder will be able to access the file. It will be available to everyone through the Development Center soon.

We would like to emphasize the changes made to BizTalk Server 2016

Deprecated & Removed List

Our education customers across the country put forth a significant effort to ensure their environments are resilient, highly available, and protected from data loss. They most commonly achieve this using backup software combined with offsite tape storage, or replication of their backups to Azure for long term storage. Often, however, I hear stories of organizations that experience dramatic and unexpected failures because of water leaks, fires, or other unexpected circumstances. These events often require more than a backup because they’ve lost significant physical equipment, or for some other reason, cannot bring their environments online even though they have backups.

Azure Site Recovery provides a true disaster recovery solution that lets these organizations bring up their replicated workloads in Azure or in their own secondary site. Azure Site Recovery can protect physical servers, Hyper-V virtual machines, VMWare virtual machines, Amazon EC2 instances, and several other workloads. Replication is fully configurable across 30 second, 5 minute, and 15 minute recovery point objectives.

The following video series describes the various use cases and walks through the process of configuring Site Recovery, replicating workloads, and testing recovery, which allows organizations to iteratively test recovery until they have a plan that is orchestrated to bring up the environment exactly the way they would want to do in a true disaster.

Video 6 and 7 coming soon!

Microsoft Flow is an easy to use product to help you set up automated workflows between your favorite apps and services to synchronize files, get notifications, collect data, and more.   In this webinar Stephen Siciliano, the group program manager, will go through how to take advantage of using Microsoft Flow for production applications

Where: https://info.microsoft.com/US-PowerBI-WBNR-FY17-11Nov-07-AnnouncingGeneralAvailabilityforMicrosoftFlow272069.html 

When: Monday 11/7/2016 10AM PST

About the Presenter:
Stephen was the Chief Design Officer of MetricsHub, a SaaS company that kept its customers’ cloud applications up and running for the lowest possible cost. MetricsHub was acquired by Microsoft in March 2013, and Stephen joined the Microsoft Azure team to develop monitoring, management and automation experiences for Azure customers, in particular Azure Autoscale and Alerts and Azure Logic Apps. In 2016 Stephen became the Group Program Manager for Microsoft Flow, an easy to use software as a service SaaS offering that enables business users easily to automate time-consuming tasks and processes.

Windows 10 Build 14959  が PCとMobileの Insider Preview First Ring 向けにリリースします。

Windows 10 Creators Update

先週、ニューヨークで開催されたイベントでWindows 10 Creators Update と Surface Studio や Surface Dial と言った新しいデバイス による、創造力に対する新たな革新とその思いお伝えしました。イベントで発表された内容の詳細についてはこちらのTerry Myerson のBlog 記事 をぜひご覧ください。先週触れた通り、WIndows とは氷山であり、皆さんが”見ている”部分というのはエンジニアが新しいUIを実現するためのワークのごく一部にすぎません。（先週リリースした Build 14955 を含む）最新のWindows Insider Build は既にCreators Update への試作として始まっています。 皆さんがイベントで見た新しいエキサイティングな機能の数々は今後数週間の中で順次お披露目していく予定です。Paint 3D Previewと言った機能は既に Insider 向けに使用できるようになっています。（ただしUS,UK,Canada、Australia, New Zealandのみ）今後2，3か月の中でInsider の皆様にCreators Update のより新しい機能をお届けすることを楽しみにしています。

Build 14959 の新機能について

Unified Update Platform : このMobile用の今回のビルドは、Unified Update Platform (UUP) と呼ばれる新しい更新システムを使って公開しています。UUPについてのより詳しい情報はBill Karagounis のBlog記事をご覧ください。

仮想マシンの画面のスケーリングのコントロール：Hyper-V の仮想マシンが時々期待通りのスケールにならないというフィードバックがあったので、デフォルトのスケーリングをパフォーマンスに合わせて100,125,150,200と言った値に設定できるように、View メニューにZoom オプションを追加しました。これにより、リモートデスクトップ接続バーがフルスクリーンモードになった時に表示されなくなるという問題も解決しました。使い勝手などについてはまだ調整中です。例えば、スクロールなしにVMの全画面を表示することが出来ないときのために、より高いDPIのズームレベルを追加しました。

その他PCに対する更新および修正項目

• 我々は画面の輝度の自動調整設定が更新後に予期せず切れてしまう問題を修正しました。その中でユーザーが自動輝度設定をした場合にその設定を変更できないという問題が再発しました。もし自動輝度設定を行っている場合はこの修正は適応されません。もし自動輝度設定を自分で設定したい場合は、設定＞システム＞ディスプレイから設定を調整してください。
• ドメイン接続したPCがドメインネットワークに接続していないばあいログインに失敗するときがある問題を修正しました。
• Outlook Main ＆Calendar などの特定のアプリで 0x800700B7 のエラーコードで更新に失敗する問題を修正しました
• 特定のデバイスのモデルでSDカードを抜いた際にシステムがクラッシュする問題を修正しました
• スポットライトロックスクリーン画像の一つを「好まない」設定した際に、すぐに別の新しい画像を表示するしてから、前の画像から次の画像への移行アニメーションが表示される問題を修正しました。
• タブレットモードで、別のアプリからアプリを起動した場合（例えば、MSNニュースアプリからWebリンクを起動した場合など）そのアプリがサイドバイサイドで同時起動せずに、フルスクリーンで起動してしまう問題を修正しました。

その他Mobileに関する更新及び修正項目

• 設定＞ネットワークとインターネット＞データデータ使用状況はパフォーマンスとUIの改善を行いました。

  image: https://winblogs.azureedge.net/win/2016/11/wp_ss_20161101_0001.png

• ウォレットにカードが追加できない問題を修正しました
• タスクスイッチャーで予期せずスタートメニューを閉じてしまう問題を修正しました
• 設定>システム電話＞既定のアプリの既定のアプリ選択のオプションが予期せず表示されない問題を修正しました
• Groobe Music など、バックグラウンドでメディアを再生しているときにバッテリーセーバーがオンになった際に音楽が止まってしまう問題を修正しました
• 一度コピー＆ペーストが正しく動作しなくなるとデバイスを再起動するまで使えなくなる問題を修正しました
• VPN設定でプリが自動的にVPN接続を行う、項目のチェックを外すとハングする問題を修正しました

PCでの既知の問題

• 3rd パーティー製のアンチウィルスソフトそふとをPCにインストールしている場合、更新できずに前のビルドにロールバックしてしまう
• ITが起動ごに数秒でクラッシュする問題についてはすでに認識しています

Mobileについての既知の問題

• 前のBuild 14951 から 14955へ更新した時の日付の変化については残っており、14955は使い続けないようにしてください。マイクロソフトアカウントのデバイスに対するチケットは今回のビルドで期限切れとなります。もし30年ずれた場合は、デバイスをリセットする必要があります。
• 追加の言語、キーボード、音声パック、を今後数週間追加でインストールすることはできません：もし既存のインストール済みの言語、キーボード、言語パックがある場合は、新しいビルドに更新しても残ります。ただ新しいものをインストールすることはできません。もしこのビルドでデバイスをハードリセットした場合、追加で言語やキーボード、音声パックを追加することが出来なくなります。その場合は、Device Recovery ToolでWindows Phone 8.1 か 10 Mobile に戻して、言語、キーボード、音声パックをインストールしてから、最新のFast Ringのビルドに更新するようにしてください。

November 2016 Bug Bash が来週スタートします！

Bug Bash の開始日を11/7(月)の AM12:01(PST) に変更しました。あなたと我々のWindowsエンジニアは同時にバグ探しを開始することになります（これまでは我々のエンジニアは先に開始していました）本日リリースする Build 14959 に対してBug Bash を実施するので、みなさんもBug Bash が始まる前にPCやPhoneを更新することが出来、クエストが公開されたと同時に開始することが出来ます。Bug Bash は11/13(日)いっぱいPST まで実施されます。我々の全チームは内部のいくつかのファンイベントとしてBug Bashing をしますので、インサイダーの皆様の参加を楽しみにしています。

もしBug Bash のQuest に対するアイディアがあったら、こちらをご覧ください。

チームの更新情報

我々はIgnite ニュージーランドから戻ってきたばかりです。多くのWindows Insider に会ってニュージーランドのコミュニティからたくさんの愛を受け取りました。多くの人が私たちのコンテンツを共有してほしいと言ってくれたのでこちらに置いておきます。キーノート：tech innovation,  Jeremiah Marble の Co-Create Community, Katharane Holdsworth の Inside Windows Insider ProgramとKyle Drunkerley へのインタビュー Insider Interviewの中のインタビューの一つとして含まれています。

我々はWindows Insider が***thonをやったと聞くのが好きです。12月にWellington でSheep -A-Thon と呼ばれるイベントがあります。もし参加したい方は、Callumに問い合わせてください。

もし何とかソンを企画したいなら、ぜひ DIY kit を見てみてください、そして多分何かしらサポートできると思います。

月曜から始まるMVPサミットでいくつかのInsider イベントを計画しており、月曜日のキーノートでBill Karagounis,Jeremiah Marble と私からプログラムとコミュニティについてお話しします。

Dona

Yes, that is right – FREE scripts and tools, created by Microsoft SQL Server Tiger PM Team (blog | twitter) are now live on Microsoft repository in github.com.

So, go to http://github.com/microsoft/tigertoolbox and enjoy the free stuff. Some notes on the solutions I’ve already used on a lot of production environments:

– SQL Server Performance baseline– probably the best solution I ever worked on the topic of performance baselining. You get a bunch of reports, pre-created for you, that you just need to deploy to a RS instance. The solution uses a distributed system of collecting data, where each monitored instance collects data on its own (in a local database). I’ve hit couple of issues with that solution though, so please be aware – you will need Kerberos configured for your RS server and might need to change some of the queries to utilize the TRY_PARSE() statements, especially on source systems that are not with different Windows Locale.

– SQL Server System Health Session PowerBI – you get a template of a PowerBI report, where you just change the source instance and immediately get visual representation of your system health session (SQL 2012+). Which means that even if you do not have any other performance collections and you need some history information on your instance – this is the thing for you. Now you have a tool to visit the history of your SQL.

– BPCheck– this is actually a must have utility for your environment. It is not something that you run on daily basis, but more like a tool you use to check your best practices and sweep your instance for issues on configuration, performance, indexing, plan caching, etc. Make sure you test before you run it on PRODUCTION though. And make sure you are aware of all the input parameters for the script!

There are over 10 different solutions/scripts/utilities at the tigertoolbox, so make sure you check them all! And test before you implement. Of course, you are also free to adapt them to your environment, as every piece of source code is OPEN for you to use!

When working with Application Insights recently in an ASP.NET application, I suddenly realised that the HTTP request and response headers weren’t included in the request data that is automatically captured. Fortunately, Application Insights has a few handy extensibility points, and this post looks at how to use one of them to include selected request and response headers along with the request events.

Application Insights has an extension point using an ITelemetryInitializer interface. By implementing this interface, you can create a class that plugs into Application Insights and is called to initialise the telemetry data before it is sent to the service.

For this scenario I created the HeaderTelemetryInitializer class as shown below. This class has a couple of properties to allow you to specify which request/response headers you want to include. In the Initialize method, it then gets the specified request and response headers (with the appropriate null checks) and adds them as custom properties for the telemetry.

    public class HeaderTelemetryInitializer : ITelemetryInitializer
    {
        public List RequestHeaders { get; set; }
        public List ResponseHeaders { get; set; }

        public HeaderTelemetryInitializer()
        {
            RequestHeaders = new List();
            ResponseHeaders = new List();
        }

        public void Initialize(ITelemetry telemetry)
        {
            var context = HttpContext.Current;
            if (context == null)
            {
                return;
            }
            if (context.Request != null)
            {
                foreach (var headerName in RequestHeaders)
                {
                    var header = context.Request.Headers[headerName];
                    if (header != null)
                    {
                        telemetry.Context.Properties.Add($"request-{headerName}", header);
                    }
                }
            }
            if (context.Response != null)
            {
                foreach (var headerName in ResponseHeaders)
                {
                    var header = context.Response.Headers[headerName];
                    if (header != null)
                    {
                        telemetry.Context.Properties.Add($"response-{headerName}", header);
                    }
                }
            }
        }
    }

Now that we have an ITelemetryInitializer, we need to register it with Application Insights when the application starts up (e.g. in Global.asax or our Startup class etc depending on which frameworks we’re using):

            TelemetryConfiguration.Active.TelemetryInitializers.Add(
                new HeaderTelemetryInitializer
                {
                    RequestHeaders =
                    {"Accept"
                    },
                    ResponseHeaders =
                    {"Content-Type"
                    }
                });

With that in place, we can run the site again and we will see the custom properties emitted for request that include the header values we asked for.

The code above is also included in a gist for easy consumption.

Enjoy!

Join us and millions of teams during International Working Out Loud Week, November 7–13, by creating a space for your team to work out loud on Yammer! Here’s how working out loud on Yammer can help your team:

• You and your teammates become more aligned with what matters—People start to reveal their assumptions, ask questions and share ideas.
• You get more work done—You won’t feel overwhelmed by too many status meetings.
• You’ll make better decisions, faster—Your team will spend less time deliberating.

As part of Office 365, Yammer helps your team get work done. Did you know that your team can create and edit documents, Excel sheets and presentations right from a Yammer group? This means keeping all your messages, files and updates in one place, where everyone can see what’s going on without the usual back-and-forth. Also, Yammer makes it easy for everyone to read the conversations that are relevant to them and skip what’s not.

Here are a few more tips to have a go at successfully working out loud on Yammer:

• Create a Yammer group—Feel free to make it private! Your teammates will feel more comfortable working out loud if they know who’s reading their messages.
• Share early. Share often—That includes updates, files and questions about your projects. Don’t wait until that deck, doc or mockup feels “done” to get feedback.
• Start a discussion—Avoid slowing your team’s progress by sending long monologues via email. Talk about each other’s updates on Yammer.
• Tsk-tsk, no cheating—Whenever you think about sending an email, post a message to the Yammer group instead.
• Celebrate your teammates—“Like” your teammates’ messages and give them “praise” for solving problems or completing tasks.

That’s it. You can kick off November 7 on Yammer by sharing and printing the infographic below. Let us know how it goes! #WOL #Yammer #wolweek

The post Work out loud on Yammer—7-day challenge appeared first on Office Blogs.

Introduction

Previously it was not possible to start processing work header that were awaiting demand replenishment since the header and not the affected lines were blocked.

This is not optimal for all situations, e.g. if the work order contained many lines and only a few needed replenishments, the warehouse workers could not start picking but had to wait for replenishment of only a few lines completed.

In this posting we are going to cover the new functionality that allows you to start a work that has some lines awaiting demand replenishment and process the lines that can be picked.

This functionality is available in Dynamics 365 for Operations (1611).

Setup

A new policy for how to control the blocking of work that has lines awaiting replenishment has been introduced on the work templates. Blocking the entire order will result in the entire work being blocking, which is similar to the existing behavior.

If you choose to block individual lines, the work will no longer be blocked and non-blocked lines can be processed.

For this posting we have chosen to set the policy to Block individual work lines.

Scenario

We are going to release a sales order for 50 ea. of item T0100 from warehouse 61. We have 10 ea. on hand at two picking locations, therefore, we need a replenishment of 30 ea.

The location directives are setup in way that allows splitting and locating what ever quantities are available at the pick locations.

After releasing the wave the work for the sales order looks like below:

UI changes

You can edit and view the policy, the number of lines that are blocked and which lines are blocked on the Work form. The policy can only be changed when the work is Open.

Note: You can use the personalization feature and add fields to the grid if you want the information to be visible there.

Work report

The work report now also includes information about how many lines are blocked.

Work execution

To begin processing the work you can use one of the different work execution Mobile device menu items.

Here we will use the User directed to pick the first two lines.

After we have picked the first two lines we are presented with the below page; assuming that the replenishment has not yet taken place and therefore the worker needs to decide what should happen next.

Note that in the example the pick line with a “needs replenishment” is the last line – however, all these lines will just be skipped if there were additional lines on the header that could be picked.

Retry

This is to support a scenario where the worker can see the replenishment is just about to happen and just wants to wait until it is done and then continue picking after replenishment. Retry will just reread the lines and return the next pick line that is not awaiting replenishment if such line is found.

Cancel

Cancel allows the warehouse worker to exit the flow so he can do something else until the replenishment is finished. The work will be kept in its current state but it is no longer locked by the current user. Hence, another worker can process the work once the replenishment is completed.

Full

When clicking Full the lines that the worker has picked are added to a new work that the warehouse worker can then continue processing. The remaining lines that await replenishment remain on the original work header. This is consistent with the standard behavior of the Full button in other flows, which is also why we decided to keep the name of the button .

Wrapping up

In this posting we have shown how you can configure your work templates in a way that allows warehouse workers to start processing work that have one or more lines that await replenishment and some that are ready for picking.

We hope you will find the functionality useful and provide your feedback.

As businesses of all sizes come to realize the value of data analytics to inform decision-making, many are also discovering the need for database solutions like Microsoft Access to help collect, organize and share data, as well as create reports that deliver valuable insights.

That’s why we’re pleased to announce today that Microsoft Access is now included in the Office 365 Business and Business Premium plans—designed to meet the needs of small and mid-size businesses. We’re also introducing an additional set of data sources that can be integrated with Access for Office 365 ProPlus, E3 and E5 subscribers.

Read on to learn more.

Database management for companies of all sizes—large and small

Access is a great database management solution for small businesses because it makes collecting and storing data accessible on the desktop—without requiring support from an IT administrator. Access enables users to develop business applications, collect and analyze data from multiple sources, and track any kind of data, from a customer contact list to robust asset management.

Soon, Access will be rolling out to Office 365 Business and Business Premium subscribers. Access will be automatically installed for these customers as part of their next regular Office client update, rolling out between December 1, 2016 and January 30, 2017. Access will continue to be included in the Office 365 ProPlus, E3 and E5 plans.

*Please note: Customers who have updates set to the Deferred Channel will receive this update in June 2017. To learn more about the Deferred Channel, see Overview of update channels for Office 365 ProPlus.

New data sources in Access

A set of new enterprise data connectors will roll out to Microsoft Access in early 2017. These new connectors include OData Feed, Dynamics CRM, Salesforce and Amazon Redshift and will be available for customers with Office 365 ProPlus, E3 and E5 plans. These new connectors will enable customers to integrate and extend Access into other line of business solutions and databases.

This is just the beginning—there are even more new data sources on the way. In the meantime, we welcome your feedback about Access. Please share your suggestions or submit requests for desired data sources on the Access UserVoice site.

The post Microsoft Access now included in Office 365 Business and Business Premium with new enhancements appeared first on Office Blogs.

With a little over one month before December 15, End of Life for the Azure Data Market “Bing Search” and “Bing Web Results Only” API offerings is quickly approaching.

At Bing we are continuously hard at work to improve our offerings and are excited that the next version of our APIs are now part of Microsoft Cognitive Services. These new APIs bring with them exciting new capabilities and will replace the Bing APIs currently available on the Azure Data Market. API releases contain important updates leading to great new experiences, more innovation and new features to delight our customers. Regular updates enable our teams to schedule changes in a predictable cadence and allow our customers to plan their work and take advantage of the new innovations, features, and industry standards in a timely manner.

Partners who are currently using the APIs via the Azure Data Market will have the option to migrate to the Microsoft Cognitive Services Search API offerings prior to December 15, 2016.

If you choose not to upgrade to the new API offering, you will automatically lose access to your existing Bing Search or Bing Web Results Only Azure subscriptions at 5:00 PM Pacific Time on December 15, 2016 and calls to these API endpoints will no longer return any data.

How to upgrade to Microsoft Cognitive Services Search API

ACTION: You will need to have upgraded to Microsoft Cognitive Services Search API before December 15, 2016.

Below are a few resources to help guide you through the process:

• Migration Guide – Upgrading From Bing API Version 2 to Version 5
• Webcast Video – How to move from Bing Search API V2 to Microsoft Cognitive Services Search API
  (Note: To access the video, click the “Register” button and enter your details.)

If you have additional questions, read through the FAQ below.

Frequently Asked Questions

Q. How do I know if I am affected by this deprecation?
A. If you are using an active Azure Data Market subscription and calling one of the Bing API end points, you are affected.

The Bing API endpoints follow the format of  https://api.datamarket.azure.com/Bing/SearchWeb/Web?Query=%27Xbox%27 (or) https://api.datamarket.azure.com/Bing/Search/Web?Query=%27New+Xbox+Games%27

Q. What will happen to my charges in general?
A. Your Azure Data Market subscription is entirely separate from your new Azure Cognitive Services subscription. After creating your Azure Cognitive Services subscription, you must cancel your Azure Data Market subscription in order to avoid being double charged. To cancel your Azure Data Market subscription, login to datamarket.azure.com or manage.windowsazure.com and cancel your Bing Search API or Bing Web results only API subscription. If you do not cancel your Azure Data Market subscription by December 15, 2016, it will be automatically canceled for you.

Q. How long will Azure Data Market Bing Search and Bing Web Results Only API be available?
A. The Bing APIs offered using Azure Data Market will be available through December 14, 2016.

Q. What are the differences between the APIs offered via Azure Data Market and APIs offered via Microsoft Cognitive Services?
A. Below is a high level summary of comparison between the two API offerings. Also the new API’s output in JSON rather than XML.  (See also the migration guide.)

Q. Where do I find the guide for migrating to the new Bing Search APIs that are part of Microsoft Cognitive Services?
A. You can find the Azure Data Market APIs to Microsoft Cognitive Services API upgrade guide here: https://msdn.microsoft.com/en-US/library/mt707570.aspx

Q. How often should I expect an API release and support for each version going forward?
A. Our current schedule for API version updates is once a year. We expect to support next versions from the launch date for a full year.  Partners are encouraged to stay current with the Bing API versions and should plan to upgrade to the latest version at least once a year.

Q. Can I use my existing Azure subscription to purchase the Microsoft Cognitive Services search offering?
A. Yes, you will be able to add Microsoft Cognitive Services paid offerings within your subscription management portal at https://ms.portal.azure.com/.

Q. How can I purchase through Microsoft Cognitive Services?
A. Within your subscription management portal (https://ms.portal.azure.com/), you can add new services within the Intelligence Category > Cognitive Services > select API type “Bing Search API.”

Q. Who should I contact for support or help with the migration?
A. You can find migration documentation at https://msdn.microsoft.com/en-US/library/mt707570.aspx.

Q. When will pricing and General Availability (GA) terms be available for the new Microsoft Cognitive Services Search API?
A. July 1, 2016

Q. Who should I contact if I have any additional follow-up questions with regards to this email and about the Microsoft Cognitive Services Search API?
A. Please visit https://cognitive.uservoice.com/ to contact us.

Our team is here to help, reach out to the Azure Support via User Voice for any additional questions.

– The Bing Search Team

With the introduction of hotfix KB # 3072929 in Dynamics AX 2012 R3, you now have the ability to utilize picking of Sales serial items with Warehouse Management processing. This functionality allows you to enable serial numbers for use only in the Sales process without actually capturing the Serial number on the Inventory transactions themselves. You have the ability to utilize this functionality if any of the following is true:

• You are operating on an AX 2012 R3 CU10 or later environment. Hotfix KB # 3072929 was introduced with R3 CU10.
• If you are operating on an AX 2012 R3 RTM, R3 CU8, or R3 CU9 environment, then you would need to install Hotfix KB # 3072929. You can find Hotfix KB # 3072929 using LCS.

The following steps articulate an example of how to use Sales serial picking with Warehouse Management processing within the context of the USMF sample company:

1. Login to USMF.

• Create a new Tracking dimension group called ‘SerialPick’ by taking the following steps:
• Go to Product information management | Setup | Dimension groups | Tracking dimension groups.
• In the Tracking dimension groups form, click New, and enter the following:

Name = SerialPick

Description = Serial – Sales process at picking

Capture serial = Picking

Register serials before consumption = unmark this

Serial number control = mark this

• In the Grid area of the Tracking dimension groups form, mark the following checkboxes for the Serial number dimension: Active in sales process, Blank issue allowed.

• Close the Tracking dimension groups form.

3.  Create a new Item that uses the ‘Serial Pick’ Tracking dimension group by taking the following steps:

• Go to Product information management | Common | Released products.
• From the Released products list page, click New | Product.
• In the Create product form, enter the following, and then click OK:

Product type = Item

Product subtype = Product

Product number = SERIALIZED

Product name = SERIALIZED

Search name = SERIALIZED

Item number = SERIALIZED

Search name = SERIALIZED

Item model group = FIFO

Item group = Audio

Storage dimension group = Ware

Tracking dimension group = SerialPick

Reservation hierarchy = Default

Inventory, Purchase, Sales and BOM units = ea

• From the Released products list page, click on the SERIALIZED item you just created, and then click Maintain | Edit.
• In the Released product details form, expand the Warehouse management fast tab, and select ‘ea’ in the Unit sequence group ID field.

• Close the Released product details form.

4.  Establish on-hand inventory for the newly created Item by taking the following steps:

• While still in the Released product details form, click the Manage inventory tab from the Action pane at the top, and then click View | On-hand inventory.
• In the On-hand form, click the Quantity adjustment button.
• In the Counting form, enter the following line:

Item number = SERIALIZED

Site = 2

Warehouse = 24

Location = BULK-005

Inventory status = Available

Quantity = 1,000.00

• Click OK out of the Counting form.
• Close the On-hand and Released product details forms.

5.  Create a Sales order for 4.00 ea by taking the following steps:

• Go to Accounts receivable | Common | Sales orders | All sales orders.
• From the All sales orders list page, click New | Sales order.
• In the Create sales order form, select ‘US-004’ from the Customer account drop-down field.
• In the Create sales order form, expand the General fast tab, and select ‘2’ in the Site field, and ‘24’ in the Warehouse field.

• Click OK out of the Create sales order pop-up form.
• In the Sales order form, enter the following line:

Item number = SERIALIZED

Quantity = 4.00

Unit = ea

Site = 2

Warehouse = 24

Unit price = 1.00

• Save the Sales order.
• Click on the Sales order line, and then click Inventory | Reservation.
• In the Reservation form, click the Reserve lot button.

• Close the Reservation form.

6.  Assign 2.00 ea of the Sales order to a WHS Load, release the Load to Warehouse, and complete the Sales picking work by taking the following steps:

• Back in the Sales order form, click the Warehouse management tab from the Action pane at the top, and then click Loads | Load planning workbench.
• In the Load planning workbench form, click on the record on the Sales lines tab, and then click Add | To new load.
• In the Load template assignment form, enter the following, and then click OK:

Load template ID = Stnd Load Template

Quantity = 2.00

• Back in the Load planning workbench form, click on the Load that was just created (NOTE: Mine is USMF-000203), and then click Release | Release to warehouse.
• Close the Infolog that opens telling you Work was created.
• Click on your Load again on the Loads fast tab, and then click Related information | Work details.
• In the Work form, take note of the Work ID. (NOTE: Mine is USMF-000203)

• Close the Work form.
• Click Control-D to open a Development workspace.
• Login to the Development workspace.
• Open the AOT, and expand Forms.
• Right-click on the WHSWorkExecute form, and then click Open.
• In the Login area, enter the following, and then click Login:

User ID = 24

Password = 1

• In the Main menu of the Mobile device, click the Outbound button.
• In the Outbound menu of the Mobile device, click the Sales picking button.
• In the Scan a Work ID License plate ID area of the Mobile device, enter the Work ID you took note of prior, and then click OK. (NOTE: Mine was USMF-000203)

• In the Sales order: pick area of the Mobile device, enter ‘NEWLP’ in the Target LP field, and then click OK.

• In the Serial number field, enter 100, and then click OK.

• In the Serial number field, enter 101, and then click OK.

• In the Sales orders: Put area of the Mobile device, click OK.

If I now go to Warehouse management | Common | Loads | All Loads and double-click on my Load ID (NOTE: Mine was USMF-000203), and then click the Sales line serials button, I’ll see my Serial Numbers 100 and 101 that were registered from my Sales pick in the Mobile Device.

Hopefully this provides an example of how you can leverage Sales picking serialization assignment with Warehouse Management processing in Dynamics AX 2012 R3.

Cloud Security Suite Brings Power and Simplicity to Securing Cloud Deployments

Microsoft and Booz Allen Hamilton are pleased to announce the general availability of Virtual Cloud Defense (VCD) for Azure Government.

Virtual Cloud Defense from Booz Allen helps Azure Government customers secure cloud workloads and protect data by deploying cost-effective cloud workload protection and security services. VCD builds upon Microsoft Azure’s unprecedented investments in cloud security and compliance and integrates third party best-of-breed, commercially available and government solutions provided through the Azure Government Marketplace to meet Federal Government and DoD security and assurance requirements.

The Virtual Cloud Defense solution enables organizations to fulfill the benefits that they expect from the cloud—improved performance and near infinite scale, agility to respond to changing demands, lower costs, and a transition from capital expenses to operational expenses for infrastructure. Whether building custom applications, migrating existing applications, or integrating commercial or government off-the-shelf solutions, deploying Virtual Cloud Defense in an organization’s environment provides immediate benefit.  Virtual Cloud Defense defines network and application architectures compliant with HIPPA, NIST and DoD cloud computing requirements, simplifies the deployment of virtual security appliances and security solutions and provides comprehensive situational awareness by providing analytics on activities within the virtual network, subnet, virtual machine guest operating systems and applications.

We welcome your comments and suggestions to help us continually improve your Azure Government experience. To stay up to date on all things Azure Government, be sure to subscribe to our RSS feed and to receive emails, click “Subscribe by Email!” on the Azure Government Blog. To experience the power of Azure Government for your organization, sign up for an Azure Government Trial.

On Friday, November 4th 2016, we started deploying another regular service update. We update production service instances in batches and it will take a take a few days for the rollout to complete.

Below is the list of the new features, improvements and bug fixes in this release.

New features

• Today we are announcing the public preview of integration of the new Azure Portal with Azure API Management. Customers can create, manage and configure their API Management instances through the new portal. Management operations currently available are scaling, VNET configuration, custom domains and SSL configuration. The new portal also gives customers easy access to existing Publisher & Developer portal features.
• SOAP pass-through general availability. After a short preview period, this feature is now generally available. Customers can host a façade for their SOAP-based APIs, gaining access to features such as developer portal, analytics and policies.

Updates and fixes

In this release we have included a number of updates that allow customers to manage certificates and cryptography in policy expressions:

• Policy expressions can now take advantage of .NET base class library cryptography types from the System.Security.Cryptography namespace.
  • SymmetricAlgorithm
  • AsymmetricAlgorithm
  • RSA
  • X509Certificates.PublicKey
  • HashAlgorithmName
  • CipherMode
  • PaddingMode
  • RSAEncryptionPadding
  • RSASignaturePadding
• Customers can now access uploaded certificates in policy expression HTTP context. Context.Deployment has a new property, Certificates, of type IReadOnlyDictionary<string, X509Certificate2>. It gives access to certificates by thumbprint.
• Policy expressions now allow the use of the byte[] type:
  • public static byte[] Encrypt(this byte[] input, SymmetricAlgorithm alg);
  • public static byte[] Encrypt(this byte[] input, SymmetricAlgorithm alg, byte[] key, byte[] iv);
  • public static byte[] Encrypt(this byte[] input, string alg, byte[] key, byte[] iv);
  • public static byte[] Decrypt(this byte[] input, SymmetricAlgorithm alg);
  • public static byte[] Decrypt(this byte[] input, SymmetricAlgorithm alg, byte[] key, byte[] iv);
  • public static byte[] Decrypt(this byte[] input, string alg, byte[] key, byte[] iv);
• The validate-jwt policy can now accept token values directly using the new token-value attribute: <validate-jwt token-value=”@( expression returns token )” />

Two days ago, we announced Microsoft Teams, the chat-based workspace in Office 365. It is a new experience that brings together people, conversations, content and the tools they need—all in one place and integrated with familiar Office applications.

As Satya says, “Every individual is different, and so is the case with every team.” We see great opportunity in helping them achieve more together—and Microsoft Teams is the open, digital environment we created to make that happen.

Watch Satya unveil Microsoft Teams in this video.

Want an exclusive look at the new product in action? Don’t miss our Modern Workplace webcast, November 15 at 8 a.m. PST / 4 p.m. GMT, titled “Bridging the Generation Gap: How to create cohesive teams.” Register here.

The post Watch Satya unveil Microsoft Teams appeared first on Office Blogs.

We hear a lot from our developers that collaborative and multi–device development is time consuming due to the need to copy packages, repositories, build folders etc. With the release of Windows 10 Creators Update, we are excited to introduce a new functionality to provide developers a faster iterative loop while building UWP apps in these scenarios– we are calling this “Register layout from network”.

In a collaborative environment designers, artists, developers, etc… can contribute to a single app layout on a network share and the effects of which will be immediately visible by all other collaborators. On the other hand, if you are building an app for multiple devices you no longer need to copy the app to each device to test the experience. For larger apps, the savings in time, on-device space and network traffic will be huge! Potentially saving hours of file transfer while testing experiences in the app!

Want to try this out?

Cool! To startyou will need the following setup –

1. Your devices must be on Windows 10 Creators Update Insider Build 14965 or later
2. You will need to enable developer mode and device discovery on all devices
3. Collaborators will need read and write access to the build folder
4. Users will only need to read access to the build folder

If you are using Visual Studio 2015 Update 3 or later with Windows 10 Anniversary Update SDK or later, you can follow the steps outlined here.

If you are using the SDK tools corresponding to the Windows 10 Creators Update, you can use  WinDeployAppCmd. Here is a sample of how it works:

WinAppDeployCmd.exe registerfiles -remotedeploydir <network path> -ip <IP Address> -pin <target machine PIN>

Network Path – Path to the app’s loose files

IP Address – enter the IP Address of the target machine here

Pin - A pin if it is required to establish a connection with the target device. (You will be prompted to retry with the -pin option if authentication is required.) Click here to learn how to get a PIN.

A couple things to note:

1. This feature is limited to PC and Xbox.
2. We recommend that the final validation be performed on a packaged app that’s signed with a trusted certificate.

We are very interested in hearing your feedback. Please post your comments or questions below.

Thanks!

Chaitanya Donthini, Program Manager – Windows Developer Platform

If you have a history with Windows, you’re probably used to using netsh to open ports on the Windows Firewall. We have a whole slew of PowerShell cmdlets to administer the Windows Firewall now and I wondered how to use PowerShell to open ports. It took me longer than it should have to do it, so I thought I’d share. In the end it is simple, but there are a lot of cmdlets to wade through, which is where I got hung up.

Here is what you’d do with netsh to open ports 80 and 443:

netsh advfirewall firewall add rule name="Open Port 80" dir=in action=allow protocol=TCP localport=80
netsh advfirewall firewall add rule name="Open Port 443" dir=in action=allow protocol=TCP localport=443

Here is how you’d open the same ports for only the Domain and Private profiles (not Public) with PowerShell:

New-NetFirewallRule -DisplayName 'HTTP(S) Inbound' -Profile @('Domain', 'Private') -Direction Inbound -Action Allow -Protocol TCP -LocalPort @('80', '443')


References
PowerShell cmdlets to manage the Windows firewall
Netsh Examples

In my previous blog entry, I mentioned that the repository at https://bitbucket.org/johnseghersmsft/ui had the version of my Multitouch event system for Unity 5.3.x.

I have now updated the repo with the 5.4 branch merged in. So simply choose the branch that matches the version you are using. The 5.4 branch has been tested with Unity 5.4.1p2.

I’ve been doing a lot of research on Service Fabric and Windows Docker Containers lately. These are natural platforms for .Net Core, which added another learning item to my list: .Net Core.
As a result, I set out to get a .Net Core WebListener web server up and running on Windows Server Core 2016. I chose Server Core because it emulates the kind of environment you’ll be faced with when running on Docker or Service Fabric, which is essentially a bare bones, no UI environment.

I’m not attempting to teach you Hyper-V, Docker, or how to get around in Server Core as they are big subjects by themselves. If you are afraid of the command line, you should not be here until you do some prerequisite learning.

Objective: Set up a .Net Core WebListener Server with SSL on Windows Server Core 2016

Start by installing Server Core 2016 in a VM. You could use a Docker container too if you’re so inclined.
Log onto the new Server Core machine. At the administrative command prompt, type
start powershell


Issue a PowerShell command to to create a self-signed cert
New-SelfSignedCertificate -CertStoreLocation Cert:LocalMachineMy -DnsName server0.contoso.com
You’ll need the cert thumbprint a little later. Mine was: C74235968895ECA9C9D50703D30CE17A7D3AEEFF

Issue a PowerShell command to create a GUID
New-guid
You’ll need this Guid to use as an AppId later. Mine was: 921328e8-5cdf-4b7f-a3cc-4e50147d1521

Switch back to your original administrative command prompt and issue these commands to create the Url ACLs (80 and 443)
netsh http add urlacl url=https://+:443/ user=Users
netsh http add urlacl url=http://+:80/ user=Users

While still in the same command prompt, issue a command to associate the cert thumb print and App Id (created above) with port 443
netsh http add sslcert ipport=0.0.0.0:443 certhash=C74235968895ECA9C9D50703D30CE17A7D3AEEFF appid={921328e8-5cdf-4b7f-a3cc-4e50147d1521}
Note: If you run the above from PowerShell rather than cmd, you may need to escape some characters to get it to work

Switch to your PowerShell prompt
Issue a PowerShell command to open 80 and 443 in the Windows Firewall. This will allow HTTP(S) traffic to WebListener.
New-NetFirewallRule -DisplayName 'HTTP(S) Inbound' -Profile @('Domain', 'Private') -Direction Inbound -Action Allow -Protocol TCP -LocalPort @('80', '443')
I opened both ports because I wanted to test both clear HTTP and HTTPS. I also chose to restrict the ports from being open on the Public firewall profile by specifying Domain and Private.

Issue a PowerShell command to download .Net Core to the machine
Invoke-WebRequest "https://go.microsoft.com/fwlink/?LinkID=827524" -OutFile .DotNetCoreSetup.exe -UseBasicParsing

In the same PowerShell prompt, install .Net Core using the following
.DotNetCoreSetup.exe /install /quiet /log .log.txt

.Net Core will silently (and very quickly) install. I chose silent because this is not a full GUI machine. When the install finishes, you should see several text log files in the directory you issued the above command from. Even though you’re on Server Core, Notepad still works and you can use it to inspect the logs and satisfy yourself that you had a successful install.
Once satisfied, I really recommend you restart the machine with this PowerShell command
Restart-Computer
You don’t need to restart, but it is a pain if you don’t let the machine pick up the environment changes.

Now we need an app. The easiest thing to adapt the one used in Getting Started. I’ll guide you through the changes. On some other friendly GUI desktop machine where you have a browser, go here and go through the article making the changes I specify below:
Skip step 1
Step 2: Complete step 2 on your Server Core machine
Step 3: Start Notepad on your Server Core machine save the same code as shown in step 3, EXCEPT change Microsoft.AspNetCore.Server.Kestrel to Microsoft.AspNetCore.Server.WebListener.
Save this as project.json in the directory you created in step 2.
Steps 4 and 5: Complete steps 4 and 5. Again you can use Notepad to create Startup.cs in the directory you created.
Step 6: Use the code specified to create Program.cs in your directory, EXCEPT replace the WebHostBuilder initialization code with this:

var host = new WebHostBuilder()
.UseWebListener()
.UseUrls("http://+:80", "https://+:443")
.UseStartup()
.Build();

Step 7: Complete step 7 as shown
Step 8: Browse to your Server Core machine name (from another machine on the network with a browser), using either HTTP or HTTPS. In my case, these were (same as the DnsName for my cert and machine):

http://server0.contoso.com/
https://server0.contoso.com/


You should have a working SSL enabled WebListener server running on Windows Server Core 2016.
Now go and brag about your bare metal, headless, command line skills.

As a final note, make sure the .UseUrls(“http://+:80”, “https://+:443”) call matches the URL ACLs you created with netsh earlier.
If you don’t, you may receive a 503 Service Unavailable from the web server.

References
ASP.Net Core Docs
Windows Server 2016
WebListener repository
WebListener ASP.Net Core Docs
Service Fabric Documentation
Containers for Windows

여러분들의 적극적인 참여를 기다리고 있습니다. 혼자 알고 있기에는 너무나 아까운 글, 소스 코드, 라이브러리를 발견하셨거나 혹은 직접 작성하셨다면 Gist나 주간닷넷 페이지를 통해 알려주세요. .NET 관련 동호회 소식도 알려주시면 주간닷넷을 통해 많은 분과 공유하도록 하겠습니다.

금주의 커뮤니티 소식

Taeyo.NET에서 http://docs.asp.net의 ASP.NET Core 문서를 한글화하여 연재하고 있습니다.

• MVC : Controller – 컨트롤러, 액션 및 액션 결과
• MVC : View – 뷰 컴포넌트(View Component)

On .NET 소식

지난 주 On .NET에는 On .NET Show가 진행되지 못했습니다.
이번 주 On .NET에서는 Rowan Miller와 함께 .NET과 Entity Framework Core 1.1 에 대해 이야기 나누었습니다.

금주의 패키지 – Bond

Bond는 구글의 Protocol Buffer와 매우 유사한 데이터 직렬화 라이브러리로써 메시지(혹은 구조체)를 연속된 비트로 만들고, 반대로 비트에서 원래의 메시지로 복원할 수 있습니다, macOS, Windows에서 동작하고 C++, C#, Python 등의 언어를 지원하지만, 개발자가 Bond를 사용하기 위해서는 아래 코드처럼 IDL과 비슷한 형식으로 먼저 스키마를 정의해야 합니다.

그 다음, 아래처럼 C# 코드를 작성합니다.

위에서 생성해 둔 라이브러리를 이용하여 객체를 초기화 한 후, 직렬화 및 역직렬화를 하실 수 있습니다.

Bond 패키지는 객체를 복사하고, 비교하기 쉬운 타입으로 정의합니다

금주의 게임 – The Gallery – Episode 1: Call of the Starseed

The Gallery – Episode 1: Call of the Starseed는 4개의 에피소드로 나누어진 판타지 어드벤처 VR 게임입니다. 게임 플레이어는 게임 속 주인공이 되어 실종된 여동생을 찾는 과정에서 신비하고 기이한 게임 캐릭터들과 만나며 모험을 펼치게 됩니다. The Gallery – Episode 1은 ‘full-room scale VR’ 방을 꽉 채우는 스케일의 가상현실에서 앉고, 서고, 웅크리고, 기는 동작 등을 통해 실감나게 게임을 즐기실 수 있습니다.

The Gallery – Episode 1: Call of the Starseed은 Cloudhead Games에서 Unity와 C#을 이용해 제작 했으며  Steam을 통해 HTC Vive에서 플레이하실 수 있고 12월에는 Oculus Home을 통해 Oculus Touch에서도 즐기실 수 있습니다.

.NET 소식

• .NET Framework Monthly Rollups Explained and .NET Framework Monthly Rollup: October 2016 : Stacey Haffner가 10월 호를 시작으로 매달 .NET Framework 업데이트 정보를 공유할 예정입니다.
• Learning .NET Core by example : Jon Hilton이 .NET Core를 쉽게 배울 수 있는 예제와 튜토리얼을 공유했습니다.
• Parallel Test Execution : Pratap Lakshman이 Parallel Test Execution에 관해 설명합니다.
• Porting Apache Avro into .NET Core : Welly Tambunan이 Avro를 Apache버전에서 .NET Core버전으로 전환하는 방법에 관해 설명합니다.
• Timing the time it takes to parse time part 1 and part 2 : Ayende Rahien이 DateTime의 데이터 형식을 효과적으로 파싱하는 방법에 관해 소개합니다.
• Microsoft IIS Administration Preview : Microsoft IIS Administration API의 프리뷰 버전이 공개되었습니다.
• Deal with time dependencies in Tests : Carlos Mendible이 테스트 시간에 따라 결과가 바뀔 수 있는 프로그램을 어떻게 정확히 테스트할 수 있는지 설명합니다.
• Metric.NET: dealing with measurement units : Ivan Milutinović이 단위 변환 오픈소스 라이브러리인 Metric.NET에 관해 소개합니다.
• MediatR Pipeline Examples : Jimmy Bogard가 Mediator pattern 라이브러리인 MediatR을 예제를 통해 소개합니다.
• Using Core class library from .NET 4.6 project : Hrvoje Hudoletnjak가 일반적인 .NET 4.6 프로젝트에서 Core용 클래스 라이브러리를 사용하는 방법에 관해 소개합니다.
• Calling UWP APIs from a Desktop Application : Mike Taulty가 Desktop Application에서 UWP API을 호출하는 방법에 관해 소개합니다.

ASP.NET 소식

• Exploring ASP.NET Core with Docker in both Linux and Windows Containers : Scott Hanselman이 Linux와 Window용 Containers에서 ASP.NET Core와  Docker에 대해 설명합니다.
• Custom authorization policies and requirements in ASP.NET Core : Andrew Lock이 ASP.NET Core에서 커스텀 인증 정책의  필요사항을  설명합니다.
• Debugging into ASP.NET Core Source : Steve Gordon이 ASP.NET Core 소스 디버깅 방법을 공유했습니다.
• Localization & Routing in ASP.NET Core 1.0 : Hisham Bin Ateya가 ASP.NET Core 1.0에 Localization과 Routing에 관해 설명합니다.
• ASP.NET Core and the Enterprise: Part 1 Frameworks : K. Scott Allen이 .NET Framework에 관해 소개합니다.

F# 소식

• Using F# on Azure : Sylvan Clebsch가 Azure에서 F#을 사용하는 방법에 관해 소개합니다.
• Getting Started with F# in Visual Studio Code with Ionide : Phillip Carter가 Visual Studio Code에서 Ionide을 이용해 F#을 사용하는 방법에 관해 소개합니다.
• Using F# with .NET Core : Ody Mbegbu가 .NET Core 환경의 F# 사용 방법을 소개합니다.
• ASP.NET Identity in an F# Web Application, Part One : Ernest Pazera가 F#의 웹 애플리케이션에ASP.NET Identity에 관해 설명합니다.
• Prefer Records of Functions to Interfaces : Matthew Doig가 F#에서 Interface 활용에 관해 설명합니다.

Xamarin 소식

• Xamarin Preview: Xamarin Profiler 0.38.0 : Adrian Murphy가 Xamarin Profiler 프리뷰 버전 0.38.0을 소개 합니다.
• Xamarin Dev Days Continue to Roll Out! : Jayme Singleton이 Xamarin Dev Days 개발 행사 일정을 공유했습니다.
• Mobile Leaders Podcast | Enterprise Mobility Trends with Maribel Lopez by Anusha Sethuraman.
• Live Webinar | Xamarin University Presents: Introduction to Xamarin with Visual Studio : Anusha Sethuraman이 모바일 전문 연구기관 Lopez Research의 창립자인 Maribel Lopez와 기업 모빌리티 트랜드에 대해서 팟캐스트를 진행했습니다.
• Understanding Android’s Doze Functionality and The Xamarin Show 6: User Interface Automation with Charles Wang : James Montemagno가 Android 절전 기능에 대해 소개하고 Xamarin Show 6에서는 사용자 인터페이스에 관해 설명합니다.
• Bringing Platform-Specific Functionality to Xamarin.Forms Apps : Pierce Boggan이 모바일 플랫폼 기존 기능을 Xamarin.Forms Apps에서 사용하는 방법에 관해 설명합니다.
• Designing Card-Based User Interfaces : Nick Babich가 카드–뷰 형태의 사용자 인터페이스 디자인에 관해 소개합니다.
• Creating A Splash Screen In Xamarin Forms and Misuses Of MessagingCenter Adam Pedley가 Xamarin Forms에서 Splash Screen 의 구현방법과 MessagingCenter의 잘못된 사용 예를 설명 합니다.
• ReactiveUI Goodies – Search and ReactiveUI Goodies – ReactiveList Jan Hannemann이 오픈소스 UI framework인 ReactiveUI를 이용한 Search 기능 구현 방법과 ObservableCollection의 일종인 ReactiveList에 관해 설명합니다.
• Semantic Versioning of Xamarin Applications : Geoffrey Huntley가 Xamarin 애플리케이션의 효과적인 버전 관리 방법을 소개합니다.
• Templates and Extensions for Xamarin & Mono : Terrence Dorsey가 Xamarin, Mono 환경에서 사용할 수 있는 여러가지 컴포넌트와 확장 기능에 대해 설명합니다.

Azure 소식

• Simpler Azure Management Libraries for .NET : Asir Selvasingh가 Azure 관리 라이브러리“Simpler Azure Management Libraries for .NET”의 개발자 프리뷰 버전을 소개합니다.
• Hosting .NET Core Services on Service Fabric : Vaijanath Angadihiremath가 Service Fabric에서 .NET Core Services를 호스트하는 방법에 관해 설명합니다.
• Running Worker Roles with Docker in .NET Core : Pepijn Schoen이 .NET Core의 도커 환경에서 Worker Roles을 실행/관리하는 방법을 설명합니다.
• ASP.NET Core 1.0 – Configure Application Insights : Joao Sousa가 ASP.NET Core 1.0에서 Application Insights 기능 설정 방법에 관해 설명합니다.
• App Service Mobile Apps .NET Client SDK 3.0.1 release : Mimi Xu가 App Service Mobile Apps .NET Client SDK 3.0.1 버전에 관해 소개합니다.
• Sending a Regular SMS with Azure Functions and Twilio : Jason Roberts가 Azure Functions과 Twilio 이용하여 메시지를 전송하는 방법에 관해 소개합니다.

Games 소식

• Curated #UnityTips No. 17 by DevDog October 2016 : DevDog가 Unity 개발에 도움이 될 수 있는 17번째 Tip을 공유했습니다.
• Unity 5 Tutorial: How to debug raycasts (video) : Gamad에서 raycasts를 디버깅하는 방법에 관해 설명합니다.
• Using InputFields with C# Unity 5.4 (video) : Learn To Be Indie가 C# Unity 5.4에 인풋필드를 설명합니다.

주간닷넷은 .NET Blog에서 매주 발행하는 The week in .NET을 번역하여 진행하고 있으며, 한글 번역 작업을 오픈에스지의 송기수 전무님의 도움을 받아 진행하고 있습니다.

송 기수, 기술 전무, 오픈에스지 현재 개발 컨설팅회사인 OpenSG의 기술이사이며 여러 산업현장에서 프로젝트를 진행중이다. 입사 전에는 교육 강사로서 삼성 멀티캠퍼스 교육센터 등에서 개발자 .NET 과정을 진행해 왔으며 2005년부터 TechED Korea, DevDays, MSDN Seminar등 개발자 컨퍼런스의 스피커로도 활동하고있다. 최근에는 하루 업무의 대다수 시간을 비주얼 스튜디오와 같이 보내며 일 년에 한 권 정도 책을 쓰고, 한달에 두 번 정도 강의를 하면 행복해질 수 있다고 믿는 ‘Happy Developer’ 이다.

The SQL Product team has identified an issue with .Net 4.6.2 framework client driver for Always Encrypted enabled database on SQL Server 2016 and Azure SQL Database. The issue can lead to intermittent failure while trying to decrypt the records from the Always Encrypted enabled database with following error message

Decryption failed. The last 10 bytes of the encrypted column encryption key are: ‘7E-0B-E6-D3-39-CE-35-86-2F-AA’.The first 10 bytes of ciphertext are: ’01-C3-D7-39-33-2F-E6-44-C3-B1′.Specified ciphertext has an invalid authentication tag. 

The above failure to decrypt may potentially lead to incorrect query results which in turn may trigger incorrect actions, for instance, incorrect updates to the database.

The SQL Product team is aware of the issue and is actively working on the fix which may be made available soon. In the interim, we have following recommendation for the users

• Users who are on .Net framework 4.6.1 are not impacted by this issue and can ignore this. We recommend not to upgrade to .Net framework 4.6.2 if you are using Always Encrypted database feature until the fix for the issue is released.
• Users who have the latest version of .Net framework 4.6.2 installed, we recommend, if possible to rollback to previous version of .Net framework 4.6.1. Note: In general, you should not uninstall any versions of the .NET Framework that are installed on your computer without testing,  because the application dependent on that version can potentially break and may not function as desired.
• If you are unable to uninstall .Net framework 4.6.2 due to application dependency, you can workaround the issue by turning of column key encryption (CEK) by setting the SqlConnection.ColumnEncryptionKeyCacheTtl property to 0 in the .Net framework 4.6.2 driver.

After uninstalling .Net framework 4.6.2 or turning off Column Encryption Key (CEK) caching, users can confirm that the error does not reappear during a table scan (e.g., SELECT * FROM < table with Always Encrypted>) executed from a query window in SSMS. Executing this scan will help validate the error doesn’t occur.

Customers who encounter the above error during the validation scan and are unable to resolve the issue, should contact sqlalwaysencrypted@microsoft.com.  The team will be able to help access and recover all previously encrypted rows that were affected by this bug. There will be no permanent data loss caused as a result of this defect.

To determine which versions of the .NET Framework are installed on a system, see How to: Determine Which .NET Framework Versions Are Installed.

Parikshit Savjani
Senior Program Manager (@talktosavjani)