#WindowsSDK

[enterinit]

Windows 10 SDK Preview Build 18970 released

Windows 10 SDK Preview Build 18970 released.

Tools Updates:

Message Compiler (mc.exe) Now detects the Unicode byte order mark (BOM) in .mc files. If the If the .mc file starts with a UTF-8 BOM, it will be read as a UTF-8 file. Otherwise, if it starts with a UTF-16LE BOM, it will be read as a UTF-16LE file. If the -u parameter was specified, it will be read as a UTF-16LE file. Otherwise, it will be read using the current code page (CP_ACP).Now avoids one-definition-rule (ODR) problems in MC-generated C/C++ ETW helpers caused by conflicting configuration macros (e.g. when two .cpp files with conflicting definitions of MCGEN_EVENTWRITETRANSFER are linked into the same binary, the MC-generated ETW helpers will now respect the definition of MCGEN_EVENTWRITETRANSFER in each .cpp file instead of arbitrarily picking one or the other). Windows Trace Preprocessor (tracewpp.exe) Now supports Unicode input (.ini, .tpl, and source code) files. Input files starting with a UTF-8 or UTF-16 byte order mark (BOM) will be read as Unicode. Input files that do not start with a BOM will be read using the current code page (CP_ACP). For backwards-compatibility, if the -UnicodeIgnore command-line parameter is specified, files starting with a UTF-16 BOM will be treated as empty.Now supports Unicode output (.tmh) files. By default, output files will be encoded using the current code page (CP_ACP). Use command-line parameters -cp:UTF-8 or -cp:UTF-16 to generate Unicode output files.Behavior change: tracewpp now converts all input text to Unicode, performs processing in Unicode, and converts output text to the specified output encoding. Earlier versions of tracewpp avoided Unicode conversions and performed text processing assuming a single-byte character set. This may lead to behavior changes in cases where the input files do not conform to the current code page. In cases where this is a problem, consider converting the input files to UTF-8 (with BOM) and/or using the -cp:UTF-8 command-line parameter to avoid encoding ambiguity. TraceLoggingProvider.h Now avoids one-definition-rule (ODR) problems caused by conflicting configuration macros (e.g. when two .cpp files with conflicting definitions of TLG_EVENT_WRITE_TRANSFER are linked into the same binary, the TraceLoggingProvider.h helpers will now respect the definition of TLG_EVENT_WRITE_TRANSFER in each .cpp file instead of arbitrarily picking one or the other).In C++ code, the TraceLoggingWrite macro has been updated to enable better code sharing between similar events using variadic templates. Signing your apps with Device Guard Signing We are making it easier for you to sign your app. Device Guard signing is a Device Guard feature that is available in Microsoft Store for Business and Education. Signing allows enterprises to guarantee every app comes from a trusted source. Our goal is to make signing your MSIX package easier.

Breaking Changes

Removal of api-ms-win-net-isolation-l1-1-0.lib In this release api-ms-win-net-isolation-l1-1-0.lib has been removed from the Windows SDK. Apps that were linking against api-ms-win-net-isolation-l1-1-0.lib can switch to OneCoreUAP.lib as a replacement. Removal of IRPROPS.LIB In this release irprops.lib has been removed from the Windows SDK. Apps that were linking against irprops.lib can switch to bthprops.lib as a drop-in replacement. Read more about API Updates, Additions and Removals here. Read the full article

[uniskiesmemo]

BlueMSX2.9.0メモ

■ BlueMSXのビルドメモ 他の人がビルドした2013年 2.8.3β https://www.msx.org/forum/msx-talk/emulation/bluemsx-latest-version 自分が弄った3倍、4倍表示対応版2.9.0β https://app.box.com/s/50a2muesr4vvii7shz1viw5ae85vpafn と、そのソース https://app.box.com/s/7uq1l4yqc2xkdwt1lifvye6c5x7nhv78 WindowsSDK7以降はDirectShow回りが変更されてるのでそのあたりの修正とか色々。 ・VC++2017かVC++2010、 ・Windows SDK 7.0か7.1 ・DirectX SDK (August 2007) でビルド完了。 ●BlueMSX最新版ソース（2.9.0？） https://sourceforge.net/p/bluemsx/code/HEAD/tree/ ステートセーブのバグその他が修正されている。 ●qedit_def.hを探してきて、qedit.hをインクルードしてる箇所をqedit_def.hに置き換え。 https://github.com/nyatla/NyWin32Capture ●Strmbaselib、Strmiids.lib、Quartz.lib WindowsSDKへのDirectShow統合に伴って、明示的なライブラリへのリンクが必要。 めんどいからこんな感じで、Win32DirectShow.cpp に pragmaで指定。 #pragma comment(lib, "Strmbase.lib") #pragma comment(lib, "Strmiids.lib") #pragma comment(lib, "Quartz.lib") ※ Strmbase.lib プロジェクトのblueMSX\Src\ThirdParty\DirectShowSamples に存在する。 インクルードパスに無ければ追加 ..\..\Src\ThirdParty\DirectShowSamples ライブラリパスに無ければ追加 ..\..\Src\ThirdParty\DirectShowSamples ※ 自分で作成する場合は、Windows SDK 7のsampleにあるbaseclassesから作れる。 http://imagingsolution.blog.fc2.com/blog-entry-189.html 自作の場合の追加のインクルードパス C:\Program Files (x86)\Microsoft SDKs\Windows\v7.1\Samples\multimedia\directshow\baseclasses 自作の場合の追加のライブラリパスに追加 C:\Program Files (x86)\Microsoft SDKs\Windows\v7.1\Samples\multimedia\directshow\baseclasses\Debug_MBCS C:\Program Files (x86)\Microsoft SDKs\Windows\v7.1\Samples\multimedia\directshow\baseclasses\Release_MBCS （※ 32ビット版Windowsの人はC:\Program Files (x86)\ → C:\Program Files\） ●zlibstat.lib zlibstat.libを要求された場合は、プロジェクト内に存在しないので zlibをダウンロードしてきてビルドして作る。 （レポジトリの過去ログを探れば見つかるかもしれない？） ●build_number.h build_number.hが見つからないといわれた場合インクルードパスに追加 ..\..\bin ●Languageファイル 英語環境向けのため、日本語環境だとうまくいかない事がある。 日本語環境でどうにかするなら、 ・エスケープシーケンス（漢字やかなの前に\があった場合の\）を削除する。 ・こまめにUTF-8で保存しなおす。 ・UTF-8で保存しなおした場合、マルチバイト文字だと再現できませんなどの警告が出るがあきらめる。 （ワイド文字対応すると結構大変そう） 英語環境でやるなら、 VisualStudioインストーラで言語を追加。 設定→環境→国際対応で英語環境を選択する。 ●その他 ・upx.exeをダウンロードしてきてパスを通しておく。 ・何か足りなかったらインクルードパス等に追加すればたぶんできる。

[teknodobra-blog]

Windows SDK için Google Analytics | Mesut Şener

Windows SDK için Google Analytics

Windows SDK için Google Analytics.Google Analytics, web siteleri ve mobil uygulamalar için en popüler analitik kütüphanelerinden biridir. Google Analytics, kullanıcı oturumlarını, ekran görünümlerini, etkinlikleri, çökmeleri, sosyal etkileşimleri ve Android ve iOS'daki tanıtım kampanyalarını izlemek için yaygın bir şekilde kullanılır. [caption id="" align="alignnone" width="512"] Google Analytics için Windows SDK[/caption] Bugün, Microsoft'un , Windows 10 geliştiricilerinin bu değerli hizmetlere erişmenin kolay bir yolunu sunan Google Analytics için bir Windows SDK başlattığını duyurmaktan heyecan duyuyoruz . SDK, bir NuGet paketi aracılığıyla uygulamalarınıza entegre edilebilir . Kaynak GitHub'da barındırılıyor . Hem Evrensel Windows Mağaza uygulamaları hem de masaüstü uygulamaları tarafından kullanılabilen bir C # SDK vardır ve C ++ veya JavaScript ile yazılmış UWP uygulamalarını hedefleyen geliştiriciler için bir C ++ WinRT bileşeni de vardır. Hem C # SDK hem de C ++ WinRT bileşeni aynı API adlarını kullanır; dolayısıyla aralarında hareket etmek kesintisizdir. SDK Google'ın üstüne inşa edilmiştir Ölçüm Protokolü , geliştiriciler HTTP istekleri üzerine Google Analytics Sunucular için nişan veri göndermek için izin veren bir hizmet. Google Analytics için Windows SDK'deki API'ler, diğer platformlarda Google Analytics'i zaten tanıyan kullanıcılar için maksimum taşınabilirlik ve okunabilirlik sağlamak için Google'ın Android SDK'sındaki sınıf adları ve tasarım kalıpları üzerine modellenmiştir.

Başlamak

Video formatı tercih ederseniz , bu " Google Analytics için Windows SDK ile Başlarken ", aşağıdaki her adımı gösterir. Yazılı formu tercih ederseniz, Google Analytics için Windows SDK'yi projenize nasıl ekleyeceğiniz aşağıda açıklanmıştır:

Uygulamanızı kaydol sizin mülkiyet kayıt, Google için zaman Analytics-, bir "Mobil uygulama" ve bir web sitesi olarak yaptığınızdan emin olun.

Uygulamanıza uygun NuGet referansını ekleyin:

C # uygulamaları için SDK .

C ++ ve JavaScript uygulamaları için SDK .

Son olarak, olayları izlemek için kodunuzu ekleyin.

Aşağıda, bir C # uygulaması için birkaç örnek verilmiştir. (JavaScript veya C ++ için yazılan örnekleri görmek isterseniz, GitHub projesi bu dillerde ek örnekler içerir.)

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

var tracker =  AnalyticsManager.Current.CreateTracker("EnterYourPropertyIdHere");

            AnalyticsManager.Current.ReportUncaughtExceptions = true;

            //create a timing event

            var screenName = "MainPage";

            TimeSpan timeSpanToLoad = TimeSpan.FromMilliseconds(237); // sample:)

            tracker.Send(HitBuilder.CreateTiming("load", screenName, timeSpanToLoad).Build());

            //Send a page view

            tracker.ScreenName = screenName;

            tracker.Send(HitBuilder.CreateScreenView().Build());

                                      // Send a userclick event

tracker.Send(HitBuilder.CreateEvent("user-events-category", "click", "sharing-button", 0).Build());

            // Send a social interaction

            tracker.Send(HitBuilder.CreateSocialInteraction("facebook", "share", "link").Build());

Yol haritası, geri besleme ve katkılar

Bu özellik açısından zengin ilk sürüm ve Windows geliştiricileri için aydınlatılan yeni özelliklerden dolayı heyecanlıyız. Biz iyileştirmeler için öneriler yanı sıra, bizim üzerinde bulmak herhangi bir sorun raporları kabul edilir GitHub . Son olarak, bunun bir açık kaynak girişimi olduğunu unutmayın. SDK'yı daha da iyi hale getirmek için sizi kendi kodunuza katkıda bulunmaya davet ediyoruz. Etiket :#AçıkKaynak, #Android, #C#, #Google, #GoogleAnalytics, #JavaScript, #Nuget, #SDK, #Windows10, #WindowsSDK Yazar: Mesut Şener kaynak : https://mesutsener.com/windows-sdk-icin-google-analytics/

[enterinit]

Windows 10 SDK Preview Build 18956 released

Windows 10 SDK Preview Build 18956 released. Tools Updates Message Compiler (mc.exe) Now detects the Unicode byte order mark (BOM) in .mc files. If the If the .mc file starts with a UTF-8 BOM, it will be read as a UTF-8 file. Otherwise, if it starts with a UTF-16LE BOM, it will be read as a UTF-16LE file. If the -u parameter was specified, it will be read as a UTF-16LE file. Otherwise, it will be read using the current code page (CP_ACP).Now avoids one-definition-rule (ODR) problems in MC-generated C/C++ ETW helpers caused by conflicting configuration macros (e.g. when two .cpp files with conflicting definitions of MCGEN_EVENTWRITETRANSFER are linked into the same binary, the MC-generated ETW helpers will now respect the definition of MCGEN_EVENTWRITETRANSFER in each .cpp file instead of arbitrarily picking one or the other). Windows Trace Preprocessor (tracewpp.exe) Now supports Unicode input (.ini, .tpl, and source code) files. Input files starting with a UTF-8 or UTF-16 byte order mark (BOM) will be read as Unicode. Input files that do not start with a BOM will be read using the current code page (CP_ACP). For backwards-compatibility, if the -UnicodeIgnore command-line parameter is specified, files starting with a UTF-16 BOM will be treated as empty.Now supports Unicode output (.tmh) files. By default, output files will be encoded using the current code page (CP_ACP). Use command-line parameters -cp:UTF-8 or -cp:UTF-16 to generate Unicode output files.Behavior change: tracewpp now converts all input text to Unicode, performs processing in Unicode, and converts output text to the specified output encoding. Earlier versions of tracewpp avoided Unicode conversions and performed text processing assuming a single-byte character set. This may lead to behavior changes in cases where the input files do not conform to the current code page. In cases where this is a problem, consider converting the input files to UTF-8 (with BOM) and/or using the -cp:UTF-8 command-line parameter to avoid encoding ambiguity. TraceLoggingProvider.h Now avoids one-definition-rule (ODR) problems caused by conflicting configuration macros (e.g. when two .cpp files with conflicting definitions of TLG_EVENT_WRITE_TRANSFER are linked into the same binary, the TraceLoggingProvider.h helpers will now respect the definition of TLG_EVENT_WRITE_TRANSFER in each .cpp file instead of arbitrarily picking one or the other).In C++ code, the TraceLoggingWrite macro has been updated to enable better code sharing between similar events using variadic templates. Signing your apps with Device Guard Signing We are making it easier for you to sign your app. Device Guard signing is a Device Guard feature that is available in Microsoft Store for Business and Education. Signing allows enterprises to guarantee every app comes from a trusted source. Our goal is to make signing your MSIX package easier. Breaking Changes Removal of IRPROPS.LIB In this release irprops.lib has been removed from the Windows SDK. Apps that were linking against irprops.lib can switch to bthprops.lib as a drop-in replacement. Read more API Updates, Additions and Removals here. Read the full article