Le Café Central de Deva
... Deva blogs!!
I changed the way of blogging, developing, designing and assisting my customers. Re-designed the site and started using the latest Windows Live Writer & Windows 10!! Additionally added Microsoft Translator gadget available @ top of page, so that you can change the page in your preferred language!!
error MSB6006: "CL.exe" exited with formula –1073741515
The same code compiled, worked successfully in Visual Studio 2010. We haven’t done any changes in Visual Studio 2013, but still we got the above error.
I fixed the issue by changing the Platform Toolset value and it helped me to compile successfully. I tried the following (refer the snapshot): Changed Platform Toolset value to Visual Studio 2013.
Visual Studio 2013
Visit the below Microsoft support lifecycle policy page to view Microsoft’s guidelines for product support from availability to end of product support lifecycle. I had added the support lifecycle policy information for the Exchange Server family of products.
For example, I enclosed Exchange Server 2010 support policy. Do you know that Mainstream support for Exchange 2010 ended at 13th of January 2015? Also it marks that Exchange 2010 entered in its extended support phase.
Hope this helps.
This December we had released the following releases – it releases include updates for Exchange Server 2013, 2010, and 2007. The following packages are now available on the Microsoft download center.
These releases represent the latest set of fixes available for each of their respective products. The releases include fixes for customer reported issues and minor feature improvements. For detailed information, you can refer Exchange team blog post.
Now you can download Visual Studio 2013 Update 4. Visual Studio 2013 updates are cumulative releases. The following download links always direct you to the latest update:
If you do not have Visual Studio 2013 (original-release version), then run one of the following downloads, both Visual Studio 2013 and Update 4 are installed.
This update includes the latest software updates and feature additions. New Technology improvements in Visual Studio 2013 Update 4 is listed in http://support.microsoft.com/kb/2994375.
In addition to that you can have a look at the below Channel 9 video featuring Robert and Dmitry Lyalin – along with special guests Aaron Bjork and Rong Lu from the engineering team – take you through the many new features, highlighting and demoing web editor improvements (HTML, CSS, JSON), various new capabilities in Team Foundation Server such as Git pull requests, updated tooling for Azure WebJobs and the new GPU usage analyzer etc.
As you know the EWS Java API, a java client library to access Exchange Web Services (EWS) - a SOAP-based API and you can use it from Java or any other language that lets you POST XML data over HTTP. The API works against Office 365 Exchange Online as well as on premises Exchange Server.
Recent update is that it’s available on GitHub as an open source project, ews-java-api and here is the official announcement for it. If you’re interested to use EWS API in your project, then you can get it started by looking at the following documentation and Mike’s post on this.
I initially installed vNext .Net Framework 4.5.2 installer in the Visual Studio 2013 environment. When I tried opening in Visual Studio 2013 but failed to see it in the “Targeted Framework” in it???
Then, try the following:– 1) Close the Visual Studio. 2) You need to download and install Developer Pack for vNext .Net Framework available!!
On successful installation, try opening the Visual Studio….!! Bingo, it’s listed now… !!
Note: + The .NET Framework 4.5.2 Developer Pack installs the multi-targeting pack for .NET Framework 4.5.2. + Developers can build applications targeting the .NET Framework 4.5.2 using either Visual Studio 2013, Visual Studio 2012 or third party IDEs. + You need to download the web installer instead of this package if you intend to redistribute .NET Framework 4.5.2.
Earlier I covered about .Net Framework vNext. In addition to that, you can try out the ASP.Net vNext, .NET Native and RyuJIT releases by installing Visual Studio 14 CTP3.
ASP.Net vNext: ASP.Net vNext is the new version of ASP.NET for web sites and services. We’ve continued to add new features and improve the development experience for ASP.NET vNext apps in Visual Studio “14”. It’s useful to recap what ASP.NET vNext offers, and why you should choose it for your next web platform. For more info, you can refer more info. For information on how to get started with ASP.NET vNext using Visual Studio “14” check out the article Getting Started with ASP.NET vNext and Visual Studio "14". .Net Native: . NET Native is integrated into Visual Studio 14 for the first time with CTP 3. This update of .NET Native also includes limited Windows Communication Foundation (WCF) support. You can now add service references to WCF services within a .NET Native app. Do you know that Windows Store apps start up to 60% faster with .NET Native and have a much smaller memory footprint. For more info, you can refer. RyuJIT: The .NET Code Generation team introduces the new, next-generation x64 compiler, codenamed RyuJIT. This new JIT is twice as fast, meaning apps compiled with RyuJIT start up to 30% faster. Moreover, the new JIT still produces great code that runs efficiently throughout the long run of a server process. For more info you can refer the following post.
Feedback: Please share your feedback at one of the following: For Visual Studio tooling related issues, please submit bugs through Connect, send suggestions on UserVoice and quick thoughts via Send-a-Smile in the Visual Studio IDE. For ASP.NET vNext, please provide feedback in Github or the ASP.NET vNext forum. Develop ASP.Net vNext apps on Mac?? Yes, check out this interesting blog post by Sayed talks about developing ASP.Net on a Mac Enjoy!!
.Net Framework vNext 4.5.2: Now you can download the .Net Framework 4.5.2 (also known as .Net Framework vNext), a highly compatible, in-place update to the .NET 4.x family (.NET 4, 4.5, and 4.5.1). It gives you the benefits of the greater stability, reliability, security and performance without any action beyond installing the .NET 4.5.2 update i.e., there is no need to recompile your application to get these benefits. For more info, you can refer.
What’s there for Developers? - Checkout the official announcement from blog post from DotNet team blog, where it tells that MS will continue to fully support .NET 4, .NET 4.5, .NET 4.5.1, and .NET 4.5.2 until January 12, 2016, this includes security updates as well as non-security technical support and hotfixes. - Beginning January 12, 2016 only .NET Framework 4.5.2 will continue receiving technical support and security updates. There is no change to the support timelines for any other .NET Framework version, including .NET 3.5 SP1, which will continue to be supported for the duration of the operating system life cycle. - For Application compatibility including .Net runtime and re-targeting changes across .Net versions, you can refer here. It’s a a great migration guide for the app developers – so check it out.
.Net Framework Support lifecycle: You can have a look at the Microsoft Support Lifecycle site for .Net Framework.
.Net Framework 4.5.2 features: For more info, about the new features in the .NET Framework 4.5.2, you can refer here.
Download: You can download the following: .NET Framework 4.5.2 Web Installer | .NET Framework 4.5.2 Offline Installer | .NET Framework 4.5.2 Language Packs | .NET Framework 4.5.2 Developer Pack.
In continuation of my earlier post, I got few additional queries how to programmatically (using MAPI) get autocomplete cache/entries for OWA 2013. I used latest MFCMAPI as a code sample to achieve this. Download latest MFCMAPI from http://mfcmapi.codeplex.com Select “Session” Menu > Select “Logon” > select profile > Open the “store” > select “Root Container” > Right click and Select “Open Associated Content table” from the menu. This will open a new window. In the same window, look for “Message Class” Column > select the entry “IPM.Configuration.Owa.AutoCompleteCache” in it > In the bottom section of the window, look out for property tag: 0x7C080102. Adding snapshot for your reference:
Hope this helps!!
On June 4th, we made available first community technology preview of the next version of Visual Studio 14. This early build is focused on enabling feedback and testing from the Visual Studio community. Based on Soma’s blog, Visual Studio "14" will most likely be available sometime in 2015, with a more complete preview release and final naming available later this year.
Visual Studio "14" Community Technology Previews (CTPs) are early, pre-release versions of the next major release of Visual Studio. CTPs provide early adopters with an opportunity to try out the new and improved product features, and the ability to share feedback with the product team. Given that this is a very early build, please install in a test environment with no earlier versions of Visual Studio installed.
New features & known issues: You can read about the new features and known issues in this first Visual Studio “14” CTP. Also, you may be interested to hear C++ improvements from Eric’s blog as well. You can download the CTP from here.
As I updated earlier, MEC 2014 concluded in Austin, Texas - MEC2014 delivered the latest content for Office 365 Exchange Online and Exchange on-premises customers. Content is delivered across tracks including: Architecture; Deployment & Migration; eDiscovery and Compliance; Exchange Extensibility; Manageability and Support; Outlook, OWA, and Mobility; and Security and Protection. Now you can get the recordings of the sessions @ http://channel9.msdn.com/events/mec/2014. Visit the sessions @Channel 9 & check it out Adding my few favorite sessions for your view…starting from its keynote session!!
Microsoft-hosted protocol plugfests provide software developers with the opportunity to learn more about the Microsoft protocols and to test their implementations of the Microsoft Open Specifications. Hosted on the Microsoft Redmond campus, each plugfest focuses on a specific task or technology area. Presentations are conducted by Microsoft engineers, who are also available for one-on-one and group discussions and to provide necessary assistance with configuration and running of the interoperability tests. Testing includes the use of protocol test suites that help evaluate whether an implementation’s protocol communications conform to the relevant Microsoft Open Specifications.
This time the Windows Server, Office and SQL Interoperability Teams are hosting a five day event at the Microsoft Redmond Campus. The event will cover topics such as; Windows File Sharing, SharePoint, Exchange, and SQL protocols.
Attendees will have the opportunity to: - Listen to presentations from Microsoft Subject Matter Experts - Windows, SharePoint, Exchange and OData session tracks - Meet with members of the Microsoft product teams -Leverage “internal” protocol test tools to test protocol implementations -Provide feedback on Microsoft’s Open Specification documentation -Get answers directly from our product teams and Microsoft Support
Hurry, you can Register book your clicking the link. On a first come, first serve basis, the first companies to register that plan to test will be provided with a private office/lab for use during the event (these fill up quickly)!!Note: The event starts @ Monday, June 16, 2014 9:00 AM and Ends @ Friday, June 20, 2014 7:00 PM; Time zone: (GMT-08:00) Pacific Time (US & Canada) ; Location: Microsoft Building 25 , Microsoft Redmond Main Campus
Are you a .Net Developer who develop custom application using Exchange Web Services (EWS) Managed API or EWS (Auto-generated proxies)? Then this is for you. The EWS Managed API provides an intuitive interface for developing client applications that use EWS. The API enables unified access to Exchange resources, while using Outlook–compatible business logic. In short, you can use the EWS Managed API to access EWS in versions of Exchange starting with Exchange Server 2007 Service Pack 1 (SP1), including Exchange Online. However, do you know that not all features that are available in EWS are implemented in the EWS Managed API?
You can refer the above snapshot or related documentation identifies the EWS Managed API feature implementations that target different versions of Exchange. If the EWS Managed API does not implement a feature that you want to use, you might consider an auto-generated proxy object model.
You can download the .Net Universe 2013 poster. This Poster showing the main .NET SDKs, libraries and packages classified by application type and package type (NuGet, official support, etc.). This poster shows how the trends are changing in .NET as we´re moving from a single large .NET Framework to a more loosely coupled and autonomous libraries and sub-frameworks, many of them even published as NuGet packages and evolving continuously. The number of those libs and packages is evolving and growing, so having a visual photo of it can be helpful. The main idea of the poster is to show that you can create any kind of application with .NET, from the largest applications to the smaller apps: in the cloud, on the web, on desktops, tablets, phones, and in embedded environments (even watches!). Any of those application types is shown as category/bucket in the poster and within each bucket we´re tossing the main libraries/SDKs/packages out. Then we´re also showing cross-cutting concerns buckets like Security, Data Access, and .NET Extension libs. The main categories are the following: - Emerging application patterns (Mobile, Web & Cloud) - Established application patterns (Desktop and Embedded) - Cross-Cutting concerns Finally, the poster is putting a check/mark on every lib/SDK bullet depending if they are or not complaint with the following: - NuGet package - Open Source - Microsoft Official Supported You can print it out or use it as in electronic format (.PDF). Using the electronic format (.PDF) allows you to access each content URL/page related.
In continuation of my earlier post on MEC 2014, you can refer the following posts to get more info on event Wrap-up @ http://blogs.technet.com/b/exchange/archive/2014/04/02/mec-2014-wrap-up.aspx & http://blogs.technet.com/b/rmilne/archive/2014/04/07/mec-2014-the-aftermath.aspx. In addition, don’t forget to view the videos of Innovation lab, Exchange through the Ages/Exhibition etc:
Finally, you can have a look at the event gallery pics @ http://www.iammec.com/Gallery.aspx
In recent headlines, the Heartbleed vulnerability in OpenSSL has received a significant amount of attention. While the discovered issue is specific to OpenSSL, many customers are wondering whether this affects Microsoft’s offerings or not. To answer that, I found a similar query posted at Microsoft forum the update – here is the forum post and answer. In addition, you can refer post at Windows Azure blog - http://blogs.msdn.com/b/windowsazure/archive/2014/04/09/information-on-microsoft-azure-and-heartbleed.aspx!! Happy reading!!
Today morning the annual developer conference, //build 2014 kick started (April 2-4) at the Moscone Center in San Francisco. It started with keynotes on the mornings of April 2 and 3 (8:30 a.m. – 11:30 a.m. PT). You can watch the keynote live stream and other sessions on Microsoft’s Channel 9 developer community site – lot of favourite sessions available in it . You can checkout @ http://channel9.msdn.com/Events/Build/2014
You can join us at Build for an unprecedented learning opportunity for developers building on the Microsoft platform. You can check the schedule, session, speaker etc @ http://channel9.msdn.com/events/build/2014
Today morning the prestigious event MEC 2014 (Microsoft Exchange Conference) kick started @ Austin, Texas. As you know MEC is the premier global event for Microsoft Exchange and Office 365 professionals to enhance their skills and meet with peers, speakers and the people who actually build and maintain the product. With hundreds of educational breakouts, interactive sessions and evening events to foster productive networking, MEC allows Exchange administrators, IT Pros and Developers to elevate their career potential and enhance their overall knowledge of Microsoft Exchange. You can refer the post @ http://blogs.technet.com/b/exchange/archive/2014/03/31/mec-is-here.aspx You can get the detailed info of MEC 2014: Session info @ http://www.iammec.com/Sessions.aspx (interesting sessions like Oslo, Clutter/Document Collaboration, Developing apps etc) Speaker info @ http://www.iammec.com/Speakers.aspx (good number of key speakers in the list) Agenda/Tracks@ http://www.iammec.com/Agenda.aspx (check it yourself) Enjoy!!
Yesterday we released the latest Exchange MAPICDO (March 2014) and its version is 08.03.0.8353.000. You can download it from @ http://www.microsoft.com/en-us/download/details.aspx?id=42040. Note: Make sure to uninstall the earlier version (if you have installed it earlier) and install the latest one. For additional info, you can refer Steve’s blog post.
Click here to download Microsoft Exchange Server 2013 Service Pack 1 (SP1). It’s version would be “15.00.0847.032”. It resolves issues that were found in previous versions of Exchange Server 2013. This update rollup is highly recommended for all Exchange Server 2013 customers. This service pack resolves the issues that are described in the support KB article http://support.microsoft.com/kb/2926248
Also, you can download the following files 32-bit /64-bit of Microsoft Office 2013 Service Pack1 (SP1) from Microsoft Download Center. Microsoft Office 2013 Service Pack 1 (SP1) provides the latest updates for Office 2013. This service pack includes two kinds of fixes:
You can download the following workbook which lists the issues that are fixed by this service pack. Microsoft Office and SharePoint 2013 Service Pack 1 Changes.xlsx. For more info you can refer: http://support.microsoft.com/kb/2817430
As you know that Exchange Web Services (EWS) Managed API provides a managed interface for developing client applications that use EWS. Click here to download the latest Microsoft Exchange Web Services Managed API 2.1(Version 15.00.0847.032).
This EWS Managed API 2.1 package contains the EWS Managed API, a managed interface for developing client applications that use EWS. The EWS Managed API simplifies the implementation of applications that communicate with versions of Exchange starting with Exchange Server 2007 Service Pack 1 (SP1). Built on the EWS SOAP protocol and Autodiscover, the EWS Managed API provides a .NET interface to EWS that is easy to learn, use, and maintain. For your convenience, the package also includes the Exchange Server 2013 token validation library. You can use the EWS Managed API and the library to build mail apps for Outlook that can be authenticated by the identity tokens issued by Exchange 2013.
As Stephen updated earlier, Dave had published series of blog posts (given below) which helps you to create Outlook profiles programmatically using MFCMAPI utility to connect Exchange Server 2013/legacy versions of Exchange, Office 365. Adding them for your reference. How to use MFCMAPI to create a MAPI profile to connect to Exchange 2013 using latest version of MAPICDO? http://blogs.msdn.com/b/dvespa/archive/2013/05/21/how-to-mfcmapi-create-mapi-profile-exchange-2013.aspx How to create an Outlook profile for Office 365 using Outlook MAPI? http://blogs.msdn.com/b/dvespa/archive/2014/01/17/how-create-outlook-profile-office-365.aspx
How to configure an Outlook profile using MFCMAPI for Exchange 2013 using Outlook MAPI? http://blogs.msdn.com/b/dvespa/archive/2014/01/16/create-outlook-profile-exchange-2013.aspx
How to use the same profile to connect to both Exchange 2013 and legacy versions of Exchange Server using latest version of MAPICDO? http://blogs.msdn.com/b/dvespa/archive/2013/05/27/omniprof.aspx Note: You can download the latest MAPICDO (May 2013 update) from http://www.microsoft.com/en-us/download/details.aspx?id=39045
Hope this helps. Enjoy!!
For those who’re interested in the K4W version 2.0 and missed the early sign up, now you have the opportunity to sign-up to another 500 participants cost of $349.00. You can have them apply here:
http://blogs.msdn.com/b/kinectforwindows/archive/2013/12/19/kinect-for-windows-expands-its-developer-preview-program.aspx Learn more and apply now Related links: http://blogs.msdn.com/b/kinectforwindows/archive/2013/11/22/thousands-of-developers-are-taking-part-in-kinect-for-windows-v2-developer-preview.aspx http://www.microsoft.com/en-us/kinectforwindows/develop/