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

BC 21 and Higher - PowerShell Cmdlet (Replacement of Business Central Administration).

Hi Readers, As discussed in last article about deprecating of Business Central Administration, there are few common actions that we use in administration till Business Central 20. For our on-prem customers, we will still require doing activities. As Microsoft suggest we need to start using PowerShell cmdlet.    Let's see how to do those via PowerShell, or Administration Shell. I will be keep adding commands as you comment to this article.

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

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.