A couple of weeks ago Microsoft Visual Studio 2010 was released. Unfortunately we will not be able to support Visual Studio 2010 in Dynamics NAV 2009 when developing SSRS (RDLC) reports.
When you are designing RDLC reports in NAV 2009 you are creating reports in a format known as the “RDL 2005” format. Both Visual Studio 2005 and 2008 supports this format, but not Visual Studio 2010. Visual Studio 2010 is able to open the “RDL 2005” format but will immediately convert the report to “RDL 2008” format. This conversion gives us the some challenges:
So to avoid this confusion we will not open up for Visual Studio 2010 support before our next major version of Dynamics NAV.
If you for other reasons want to use Visual Studio 2010 you can easily have Visual Studio 2008 and Visual Studio 2010 installed on the same machine. We will just open the Visual Studio 2008 version when you select “View / Layout” in the Object Designer.
If you only have Visual Studio 2010 installed you will see this message:
“An error occurred when opening Report Designer. A supported version of Visual Studio could not be found.“
This is the same message you get when you have no Visual Studio installed, because we search for the following Visual Studio versions and in prioritized order. So in case you have both Visual Studio 2005 and 2008 installed, we will use the 2008 version:
In a previous blog post I outlined the Visual Studio options you have for designing RDLC reports for NAV 2009, and this list is still valid.
Hint: If you are using Windows 7 and want to use “Microsoft SQL Server 2008 Express with Advanced Services ” you need to install “Microsoft SQL Server 2008 R2 Express with Advanced Services” to have a successful installation.
Claus Lundstrøm, Program Manager, Microsoft Dynamics NAV
Have you ever submitted feedback on a page in the MSDN library for Dynamics NAV and wondered what happens to it? If you give a rating by clicking the stars in the top right corner of any topic, a feedback text box opens.*
You click Send, and then what?
We read and analyze every piece of feedback that comes in. We look at ratings for individual topics, average ratings for all NAV Developer and IT Pro Help that is published on MSDN, and changes in ratings over time. Unfortunately, we don't get very many ratings, but we use whatever we get. We also review the text feedback. Here's how we've categorized all 46 comments that we've gotten since we started publishing content on MSDN in December of 2008:
Let me explain a little more about the "No Action" pieces of feedback. Out of those 26, we categorized 6 as "negative," 11 as "positive" and 9 as “neutral.” We still learn something about what's helpful or not helpful to you from (almost) all pieces of feedback, but they don't require any action from us.
Here are a few examples of text feedback that we’ve received.
You told us that the topic How to: Redesign Matrix Forms was "not thorough, there should have been more detail." So we added a new Walkthrough about redesigning a matrix form and linked from How to: Redesign Matrix Forms to the new Walkthrough. This feedback now goes in the Fixed bucket.
The "neutral" No Action bucket usually contains incomplete comments. We’ve gotten comments like "..." or "ths." Another example of neutral feedback is a comment about MSDN, not about NAV Help, such as "ScriptFree is much easier to read and navigate." (Yeah, I like the Lightweight and ScriptFree options for the MSDN experience, too!)
The feedback in the "positive" No Action bucket makes my day. It's great to hear that topics are helpful. Comments like, "excellent article, explained well and clear, very helpful" or "good one" are a nice pat on the back for me and the other writers. We track these as an indication of what areas of Help to continue to focus on in future versions.
The ones in the "negative" No Action bucket are the most difficult. The information that "This is a hopeless article" or that a topic is "bad" or occasionally, a word that is not fit to print here, is definitely good information. We know we've missed the mark. But there's not enough information to know exactly what you didn't like or what we can do to improve the topic. That's why these go into the no action bucket. I wish I could chat with everyone who submitted something that lands in this bucket and ask for more detail. We can tell you're frustrated with the topic and we want to help, just tell us how!
The next time you read something in the MSDN library, take a second to give us your honest feedback. We’re listening!
UPDATE July 23, 2010
*Only the Classic view on MSDN has the "Click to Rate and Give Feedback" stars. If you are using the Lightweight view, click Preferences in the top right corner, select Classic, and then click OK to switch to the Classic view. If you are using the ScriptFree view, click Classic in the top right corner to switch the view. Now you can submit your feedback about Microsoft Dynamics NAV Help.
Calling all Convergence-Atlanta-bound partners! Training feedback wanted!
Join the Microsoft Dynamics Worldwide Partner Readiness team at a roundtable discussion on April 26, from 3:30-4:30 pm at the Atlanta Omni Hotel. We'd like to get YOUR feedback on readiness training.
For more details and to RSVP, please contact firstname.lastname@example.org.
Convergence Atlanta 2010
Check out the updated Microsoft Dynamics NAV Test Drive site, where potential customers can log onto our Test Drive environment using their web browser and experience Microsoft Dynamics NAV 2009 first hand without the need of installing it themselves. On the site, you'll also find case studies, demos, videos, white papers, and other resources for learning about Microsoft Dynamics NAV solutions.