Skip to main content

NAV 2013 - Visual Studio Component Require for Report Development.

Hi all,

As a developer we have to work on various versions of Navision. This task may contain RTC Report Development.

As we all are aware that Every version (2009 Onward) supports different versions of Visual studio for Report development.



I personally have three versions of visual studio installed for Report Development -

Visual Studio 2005 - Report Development in NAV 2009 SP1.
Visual Studio 2008 - Report Development in NAV 2009 R2.
Visual Studio 2010 - Report Development in NAV 2013.

All these consumes pretty good space in my machine will all the features, which i have either not used ever or used once or twice.

So why to install complete Visual studio just for report development?

While going through Report Development guidelines from Microsoft i came across Minimum component required for Report Development.



So If you will only be working on RTC Report Development, install only selected component.

Regards,
Saurav Dhyani
www.sauravdhyani.com

Comments

Popular posts from this blog

Microsoft Dynamics NAV 2016 - How to Configure Phone Client.

Hi All, In this article we will discuss how we can connect Microsoft Dynamics NAV 2016 with New Client Launched i.e. Phone Client. This Article Contain Steps for a Android Phone as I have Only Android Phone. I am doing it having all tiers on my windows 8 machine, steps remain same for multiple servers but issues might be different. What we Need (Other what we discuss in this article) -  The Service Tier should be on Public IP . Some of the Data-card does not Provide you Public IP. check it for sure.

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.

🚀 Exploring Vibe Coding with GitHub Copilot for Business Central.

Hi All, In a recent #BCOpenDiscussion session, we delved into the fascinating concept of Vibe Coding —a new way of building software where developers collaborate with AI (like GitHub Copilot) to co-create solutions.  The session covered practical setup, how AI understands context, and even touched on Microsoft's new Model Context Protocol (MCP) integration for enhanced learning. Let’s break down the journey, step by step.