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!! Additionally added Microsoft Translator gadget available @ top of page, so that you can change the page in your preferred language!!
The Microsoft Office Configuration Analyzer Tool (OffCAT) 2.0 provides a quick and easy way to analyze Microsoft Office programs for known configurations that cause problems. Now with latest OffCAT 2.0, it provides a detailed report of your installed Office programs. This report includes many parameters about your Office program configuration and highlights known problems found when OffCAT scans your computer. For any problems that are listed in the report, you are provided with a link to a public-facing article (usually a Microsoft Knowledge Base article) on the issue so you can read about possible fixes for the problem. If you are a Help Desk professional, you can also save the report to file so that the results can be viewed in the Office Configuration Analyzer Tool on another client where the tool is installed. The Office Configuration Analyzer Tool also includes a command-line version that can be used to collect an OffCAT scan without user intervention.
By downloading OffCAT.msi for OffCAT 2.0, you are hereby consenting to the installation of this program to analyze select Microsoft Office programs on your computer. You can download it from http://www.microsoft.com/en-us/download/details.aspx?id=36852 Install it at the machine which you want to troubleshoot:
Are you planning an upgrade to Microsoft Exchange Server 2013, or do you want to know more about what it would involve? Would you like help preparing for Exam 70-341 or Exam 70-342? Take this fast-paced, demo-rich Jump Start course, and learn about planning, deploying, and managing Microsoft Exchange Server 2013 Exchange on-premises.
You’ll find out how to manage the messaging infrastructure and provide high availability and security through demos geared to your business needs. This Jump Start is appropriate for anyone upgrading from earlier versions of Exchange, and gives as well as IT Pros who have prior networking experience the Microsoft Exchange training they need. You can visit Microsoft Virtual Academy’s Core Solutions of Exchange Server 2013 Jump Start.
This Jump Start is appropriate for anyone upgrading from earlier versions of Exchange as well as IT Pros new to Exchange but with prior networking experience. If you are pursuing the MCSE: Messaging certification, it will help you prepare for Exam 70-341.
Full course outline:
So, make use of it
Have a look at the First look blog about the upcoming Exchange Server 2016 published at Exchange team blog - it talks about Microsoft Exchange Server 2016 & Ignite conference… Interestingly it also points that you’ll be able to watch recordings of all sessions—including the Meet Exchange Server 2016 overview and all the Exchange sessions—on the Web within 48 hours after they happen.
Recently I got requests from the developer community regarding my earlier article – so I take this opportunity to point how you can explore more about Microsoft Exchange Server Protocols. As you know through the Open Specifications program, Microsoft is helping developers open new opportunities by making technical documents related to interoperability for certain popular Microsoft products available to view and download from MSDN at no charge. Although the technical documents are freely available, many of them include patented inventions. Some of these patents are available at no charge under the Open Specifications Promise or the Microsoft Community Promise. The remaining patents are available through various licensing programs. For more information, please visit the Open Specifications Dev Center website.
Exchange Server Protocols Overview Document: It provides information about the protocols and other technologies that are included in the Exchange Server Protocols documentation set and the relationships among those technologies.
Exchange Server Protocols Technical Documents: It provides detailed technical specifications for Microsoft proprietary protocols (including extensions to industry-standard or other published protocols) and other technologies that are used by Exchange Server to communicate with other Microsoft products.
If you got any questions on these documents then please reach out to the related MSDN Forums: http://go.microsoft.com/fwlink/?LinkId=330023. Also you can have a look at the blogs authored by the engineers who support Open Specification documents.
Hope this helps.
Now you can download Office Lens Preview app for iPhone & Android Phones, a handy capture app that turns your smartphone into a pocket scanner. It crops, straightens, enhances, and makes pictures of whiteboards and documents readable. Pictures of documents can be saved to OneDrive and editable on any device.
In my day-today-life, I am already using the Windows Phone app for a while now and it’s simple, great handy app to use:
You can have a look at the following videos for the respective ones:
Office Lens Preview for iPhone:
So now its your turn - use this app with your respective mobile versions and see it helps you to improve the productivity as well. For more info, you can refer: https://blogs.office.com/2015/04/02/office-lens-comes-to-iphone-and-android/ Happy Productivity!!
Now you can download the Office 365 API Tools, which enable developers to integrate Office 365 services such as mail, calendar, contacts, files, users and groups into their applications. The best part is now it’s integrated with Office Developer Tools for Visual Studio 2013 - November 2014 Update. Now with this, you can integrate your applications with Office 365 services such as mail, calendar, contacts, files and more. This extension will help register your application to consume Office 365 APIs, and will add the necessary NuGet libraries to get you up and running in no time.
Like earlier, I was involved in migration of VS 2013 C++ Outlook add-in project which was created in Visual Studio 2010. During the compilation I encountered the following error:
In general, CL.exe is Visual Studio Compiler. So it should be in your Visual Studio installation directory. if there is no cl.exe in the directory, then either you can repair or reinstall the Visual Studio.
I tried the earlier trick, but it haven’t worked for me - I tried changing the Platform toolset, but it haven’t worked. Then I fixed the issue by pointing the Executable directories path to the place where CL.exe exists. Check “Configuration Properties” > “VC++ Directories” > “Executable directories” and add the path.
Adding the snapshot as well for your reference:
After setting the correct path, the compilation went without any issue. Happy debugging!!
As I updated earlier, the Visual Studio Community 2013 community edition is a new, full-featured, and FREE addition to the Visual Studio product lineup. Enclosing the following demo that highlight multi-device apps across Windows, Android, and iOS, and that show how Visual Studio Community can be extended to support additional languages like Python. Join Scott Hanselman, Dmitry Lyalin and members of the product team to see how this community edition includes capabilities that are perfect for individual developers, students, open source contributors, and small teams.
Now you can download Visual Studio Community 2013. It’s a full featured IDE for FREE – Yes, it’s
It contains that all you need. So what it all contains:-
In short, using Visual Studio Community 2013, you can code faster than ever with an advanced code editor and seamless debugging. The power of the cloud, state-of-the-art tools, and agile development services provide you with the most comprehensive free developer offering ever! So you can start coding the app of your dreams for Windows, Android, and iOS using that.
Download: http://go.microsoft.com/fwlink/?LinkId=517284 Q&A and System requirements: Check out - https://www.visualstudio.com/products/visual-studio-community-vs.aspx and the one I like the below….
Dear Azure application developers, Join the virtual event to watch as Scott Guthrie announces an exciting new Microsoft Azure service for application developers. So Save the date and Add to Calendar
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.
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.