ssdt 2012 and ssdt 2010 partnering with vs 2010

  • Thread starter Thread starter db042190
  • Start date Start date
D

db042190

Guest
Hi. We have a server that runs on the windows server 2008 r2 standard os. We use it a lot to do vs2010 development for ssrs and some ssis. From what I can tell it is using ssdt 2012. And most people do well there except for a few of us where vs2010 occasionally tells us its shutting down in the middle of our work and where other weird things happen as well. Even when we run vs2010 as admin. I think MS has been looking at the problem for a few months now. TFS is hooked in there.

So until the problem is fixed, we had the bright idea of installing vs2010 on installed virtual desktops. We cant go local cuz we are switching over to win 10 on our locals where vs2010 wont run. The virtual desktops run win 7.

I made the mistake of requesting ssdt 2012 be installed on the virtual only to learn ssdt 2012 isn't compatible with win 7. I think that install also automatically installed vs 2012.

So I'll request that any vs or ssdt higher than 2010 be uninstalled and i'll try having ssdt 2010 installed instead. And i'll hook the same TFS into the virtual desktop's vs instance probably with directory mappings that are different from the ones I used to use on the server.

Whew! So the question is, if I check out an rdl (on the virtual) that was last updated with ssdt 2012 (on the server), and make changes will I have a problem using ssdt 2010? And similarly, will my coworkers who still work on the server have any problems making changes to the same rdl using ssdt 2012? And checking those in? I have to double check but I believe the rdl's get deployed to a sql 2016 server. and the dtsx's to a 2012 server.

Continue reading...
 
Back
Top