SP1 compatability with recently released Microsoft products

IF t(release of new versions of new products) > t(release of NAV 2009 SP1) THEN 
  DontCountOnIt := TRUE;

NAV2009SP1 is not compatible with VS2010, that's for sure.

Regarding Office and Exchange, I think that there is no problem... but of course not "official compatible"...

Silverlight, ASP, SSRS - all depends on how you are using it, and there cannot be something like "official compatible" - those are generic tools and thus you can use them in compatible way or in noncompatible way... I can say that SSRS is Navision 2.60 comatible if you want (you can create report over the data on SQL...)...

davmac1 wrote:

I was hoping for some knowledge not Sunday humor

You've been on mibuso long enough that this WAS in fact knowledge, just wrapped around a cute way of saying "when Microsoft releases new products, compatibility with other products is not always a given". Expect problems, verify with your MSFT contact before implementing new versions, especially when they are released after your NAV version.

Tell me though, how would you approach them dealing with this issue? How do you think they can have an efficient plan to check for compatibility across their product lines every time a new version comes out? How do you propose that the Visual Studio team releases services packs for all other products to make those compatible? Are you suggesting that every product team has a team of people ensuring compatibility wth all other MSFT products?

I'm not defending incompatible products, just recognizing that it might not be all that easy to manage.

davmac1 wrote:

... the new stack products.

Hmmm, "stack", the only people that say that are the propaganda people at microsoft. You should really take a couple of buckets of metaphorical salt to those meetings. Or you might get swept into bankruptcy by "dumb and dumber".

davmac1 wrote:

It seems we are always way behind the technology curve on new Microsoft product updates.
Are we always destined to be 6 to 12 months behind?
I have heard about VS 2010 breaking NAV. I have heard that SQL Server 2008 R2 breaks the NAV RTC reports.
Have their been any fixes?

Sorry accounting systems aren't sexy, the marketeers don't like them so they don't demo them. So Microsoft doesn't "dog food" NAV. In addition Microsoft seem to be treating NAV as an application not a development tool. So you get the "ship it anyway" mentality. Unfortunately, it seems that enough people fall for the hype to make it worthwhile to ship the dev tools too in recent times. Witness the sexy but broken additions to MS-SQL over the last few years.

The minimum requirement for Nav report editing is:

Visual studio express 2008, web developer.
and
Microsoft Report Viewer Add-on for Visual Web Developer 2008 Express Edition

Files should be available on ms downloads:

en_visual_studio_2008_express_with_service_pack_1_x86_dvd_x15-04728.iso
VWD_RV_Addon_enu.exe

And yes, they're 'free'.

mthomsen wrote:

We recently did two blog posts on this topic:

* SQL Server / Visual Studio:
http://blogs.msdn.com/b/nav/archive/201 ... -2010.aspx

* Office / SharePoint:
http://blogs.msdn.com/b/nav/archive/201 ... -2010.aspx

Regards, Michael

Hi Michael,

Is the NAV 2009 R2 also compatible with Office 2010? Is there any company that has been used NAV 2009 R2 with Office 2010? Thank You.