April 5, 2017
.NET, .NET 4.7, .NET Core 1.0, .NET Framework, .NET Framework 4.5.2, .NET Framework 4.6, .NET Framework 4.7, ASP.NET, ASP.NET Core 1.0, ASP.NET MVC, C#.NET, Microsoft, Troubleshooting, Visual Studio 2017, VisualStudio, VS2017, WCF, Windows, Windows 10
I was frustrated by this error when I am trying to reinstall Visual Studio 2017 after my visual studio got corrupted/failed during upgrade to 15.1 ( or after a previous installation failed due to low disk space).
There is a file called ‘state.json’ , in below mentioned path, which is creating this particular issue.
- Delete/rename the folder as is or rename ‘state.json’ file to ‘something.json’ .
Found from : https://developercommunity.visualstudio.com/content/problem/2877/install-error-0x80131500-failed-to-deserialize-pac.html
April 2, 2017
.NET, .NET Framework, Add-In's, App Service, Azure, Azure SDK, Azure SDK Tools, Cloud Services, General, Microsoft, Microsoft SDKs, Visual Studio 2013, Visual Studio 2015, Visual Studio 2017, VS2013, VS2015, VS2017, Windows 10, Windows 7, Windows 8.1, Windows Azure, Windows Azure Development, Windowz Azure
Windows Azure SDK for .NET, which include SDKs, basic tools, and extended tools for Visual Studio development for Azure Cloud enabled applications. Microsoft has released latest Azure SDK for .NET along with Visual Studio 2017 (RTW). The new version v3.0 will support only Visual Studio 2015/2017, if you are using Visual Studio 2013 you can use Azure SDK for .NET v2.9.6.
You can have both the version side by side, by uninstalling earlier version first for Visual Studio 2013 and installing latest version to support newer visual studio.
There is not much major changes included in this release:
- All the tools you need to do Azure development will be part of Visual Studio 2017 going forward.
- For Visual Studio 2015 the SDK will still be available through WebPI.
- Microsoft have discontinued Azure SDK for .NET releases for Visual Studio 2013 now that Visual Studio 2017 has been released.
Download: Azure SDK for .NET 3.0 – VS 2015 | VS 2013 (v2.9.6 ) | All Versions (including Java/Node.JS)
In my earlier article, I shared the details to download various Visual Studio Editions. This is an online installer which would require associated packages to be downloaded from online Microsoft sources. Means Microsoft is not providing an Offline ISO as a download like in Visual Studio 2015. This would be a time consuming process depending of the packages you have selected to install and your internet bandwidth provided by your ISP.
With this few steps I am going to walk you through necessary steps to download all necessary packages to create an offline installer. Depending on the modules you select, package size may grow up to ~23GB.
First Step: you would need to download associated installer bootstrapped file.
||Setup File Name
|Visual Studio Enterprise
||vs_enterprise.exe –layout c:\vs2017offline –lang en-US
|Visual Studio Professional
||vs_professional.exe –layout c:\vs2017offline –lang en-US
|Visual Studio Community
||vs_community.exe –layout c:\vs2017offline –lang en-US
Second Step: Go to the folder where you have saved the associated exe. Open Command Prompt(CMD.EXE) and execute the associated command for the related executable for the edition you want to create offline setup for.
It would take a while to complete the download of all packages.
Final Step: Once the above step is completed, without errors, you can find that you yourself has created an offline installer. Take a back to external USB for later use or copy to other machines as necessary.
Now go to “c:\vs2017offline “ and run the associated exe and select the options you would need to install. It would get installed faster, and you can reuse the same installer multiple times without the need of downloading every time.
You can learn more about additional switches to download only what is needed here
March 7, 2017
.NET, .NET Core 1.0, .NET Core 1.0.1, .NET Framework, .NET Framework 4.6, ASP.NET, ASP.NET 4.5, ASP.NET AJAX, ASP.NET Core 1.0, ASP.NET Core 1.0.1, Azure Tools, C#.NET, KnowledgeBase, Microsoft, SignalR, Visual Studio 2017, VisualStudio, VS2017, Web API, Web API v2.0, Windows, Windows 10
Microsoft has released today the latest version of Visual Studio.
The new Visual Studio 2017 will help you develop apps for Android, iOS, Windows, Web, and Cloud. It will also help you use version management, be agile, and collaborate effectively.
Includes support for Xcode 8.3, iOS 10.3, watchOS 3.2, and tvOS 10.2 tools and APIs in the Xamarin.VS Extension for Visual Studio 2017..
To know more about all the features included, please go through What’s New in Visual Studio 2017
December 9, 2016
.NET, AMQP, Analytics, Azure, C#.NET, Cloud to Device, Communication Protocols, Connected, Connectivity, Contrained Networks/Devices, Device to Cloud, Device Twin, Emerging Technologies, Geolocation, HTTP 1.1, Identity of Things (IDoT), Internet Appliance, IoT, IoT Hub, IoT Privacy, IoT Security, KnowledgeBase, machine-to-machine (M2M), Machines, Microsoft, MQTT, Stream Analytics, Visual Studio 2015, Visual Studio 2017, Visual Studio Code, VisualStudio, VS2015, VS2017, Windows, Windows 10, Windowz Azure
IoT Hub is a fully managed service from Microsoft Azure as part of Azure IoT Suite that enables reliable and secure bi-directional communications between millions of IoT devices and your solution back end.
Azure IoT Hub are designed to provide following capabilities:
- Multiple device-to-cloud and cloud-to-device communication options, including one-way messaging, file transfer, and request-reply methods.
- Built-in declarative message routing to other Azure services.
- A queryable store for device metadata and synchronized state information.
- Secure communications and access control using per-device security keys or X.509 certificates.
- Extensive monitoring for device connectivity and device identity management events.
- Provides device libraries for the most popular languages and platforms.
IoT Hub and the device libraries help you to meet the challenges of how to reliably and securely connect devices to the solution back end.
Real-world IoT devices mostly have the following constaints:
- Embedded systems.with minimal or no user interaction.
- Remotely available, with less physical access. .
- Reachable through the solution back end.
- Limited power and processing capabilities
- Intermittent, slow, or expensive network connectivity.
- Use proprietary, custom, or industry-specific application protocols.
- Created using a large set of popular hardware and software platforms.
IoT Hub provide solutions to meet all the above constraints of a connected device. In addition it also provides scale, scalability and reliability. It also addresses most of the connectivity challenges through following capabilities.
- Device Twin: With Device twins, you can store, synchronize, and query device metadata and state information, and these are stored in JSON format. IoT Hub persists a device twin for each device that you connect to IoT Hub. This feature was introduced in Novemeber’16 with General availability of Iot Hub.
- Per-device authentication and secure connectivity. You can provision each device with its own security key to enable it to connect to IoT Hub.There by enabling you to manage or block devices as desired.
- Route device-to-cloud messages to Azure services based on declarative rules. IoT Hub enables you to define message routes based on routing rules to control where your hub sends device-to-cloud messages.
- Monitoring of device connectivity operations. You can receive detailed operation logs about device identity management operations and device connectivity events.
- Support for latest and widely used IoT protocols and provides extensibility: Protocols such as AMQP 1.1 or HTTP 1.1 and MQTT 3.1 are supported. We could also provide additional protocol translation using Azure IoT Gateway SDK at Device/Field/Protocol Gateway layer.
Azure IoT Hub can bring more value to organizations to bring in their field devices to cloud with real-time data capture and bi-directional communication. It solves the problem of lack of proper communication infrastructure for devices to communicate or operate on real-time basis. Pay per use, less investment infrastructure that would let you scale as you grow.
Do you feel some similarities between IoT Hub and Event Hubs service already exists as part of Azure Platform? In my later articles I would be covering some of the major differences.