Deploy BizTalk 2010 Map (btm) to BizTalk 2006 R2 server? - biztalk

I know it is not a normal practice for someone to deploy 2010 map to 2006 server but I have no choice. The questions I have is "Can I deploy a 2010 map to 2006 R2 server"? It seemed to me that since they are both btm files, the only difference between 2010 and 2006 mapper is in the UI, not the generated maps. But, I'm not sure if that is true, and before I can deploy this to production server, I need to be sure.

After some research and experiment, I figured it out. Apparently, the btm file used by the 2006 mapper and 2010 mapper are both the same format. So, copying myMap.btm file from a 2010 project and adding (existing item) to the 2006 project did the trick. I am almost sure this will work coversely too although I have not tried it. Anyways, I compiled the project, and got my 2006 map dlls, and my boss was happy :)

Related

Visual Studio 2015 - Report Viewer 2015 redistributable - Getting Report Viewer "12" working

I'm running SQL 2014, and some users are having problems with the Report Viewer 11 control (Redistributable 2012), so I want to give the "Report Viewer 12" new control (Report Viewer Redistributable 2015) a spin. But this doesn't seem to be working from the steps I've tried so far, and as of the time I'm writing this there seems limited information on the newer control, and just information of workarounds for the old one.
Anyone get this new one working? Steps to Reproduce?
I'm looking into the solution, and it appears adding the feature via the installer (SQL Data tools) should help. But I'm surprised there is not Nuget Package or etc. And such little documentation covering the new version. Too Bleeding edge?
Update: I installed SQL Data Tools via 2015 installer (modified installation and choose new feature). But now I'm jumping a couple more hurdles.
Ok, so I did get this working...
I modified the VS 2015 installation to add SQL Data Tools
I uninstalled the Nuget Package for 11, because we want 12
I added a reference to Microsoft.Reporting.Web (12) which was an option thanks to step 1
I updated any left over references in my Web.config from version 11 to version 12
I created a new fresh form.aspx
I added a script manager
Via the design view I dragged a 12 report viewer control onto my page
I configured the report viewer as I regularly would
asp:ScriptManager ID="ScriptManager1" runat="server">/asp:ScriptManager>

Visual Studio 2013 Update 2 : Editing TypeScript files are very slow

We have been using TypeScript in our project since last year with VS 2012. Recently we upgraded to VS 2013 Pro Update 2 and now if we work on TypeScript the IDE performance is extremely slow (particularly the save file).
Also once I open a TypeScript file the IDE becomes slower for all the files (cshtml, js, cs) in that web project.
I found the following article to improve the performance of VS 2013 but it did not work.
Why is VS 2013 very slow?
This problem was never there with VS 2012. Is there any workaround for this issue?
Update: We now know that the problem is with AnkhSVN plugin that we are using in VS 2013.
https://typescript.codeplex.com/workitem/2506
If we disable this plugin then this problem disappears. But this workaround is not convenient as we still need AnkhSVN to track changes in VS 2013.
This problem was never there with VS 2012. Is there any workaround for this issue?
One workaround would be to try disabling the compile on save option for TypeScript. If that helps you might want to investigate some thing like https://github.com/grunt-ts/grunt-ts
I took the VS 2013 Update 3 RC today and it fixed this issue.
http://www.microsoft.com/en-us/download/details.aspx?id=43398

Copying file from Unix to Sharepoint 2010

I need to copy a file from Unix to Sharepoint 2010 team site... Is there an API that does that? If not, what is the best way to accomplish this?
SharePoint 2010 provides a number of SOAP based web services that you can call to upload files, manipulate list items, etc. See here for more information: http://msdn.microsoft.com/en-us/library/ee705814.aspx
Alternatively, SharePoint 2010 provides UNC path access to document libraries. For example, you can access a document library located at http://myserver/mysite/mylibrary by \\myserver\mysite\mylibrary. How you would do this from a UNIX machine, I don't know, but hopefully that points you in the right direction.

Visual Studio 2008 IDE freezes/crashes when opening .aspx file with css included [duplicate]

This question already has answers here:
Visual Studio 2008 hangs while opening aspx/ascx file
(10 answers)
Closed 7 years ago.
Visual Studio (SP1) runs fine until I try and view .aspx source files with the lines
<style type="text/css">
</stlye>
anywhere in them, upon which it freezes (i.e is totally unresponsive) and I have to use the task manager to shut it down.
I have read a lot of questions about Visual Studio 2008 crashing on viewing some source files. However, I still can't fix this problem.
I have systematically deleted and re-included all other code and it comes down to these two lines, which is very confusing. Sometimes it happens as soon as the lines are added, sometimes it doesn't freeze until I build the solution with any of the problem pages open. I can add external style sheets, and it only started recently.
I had Resharper 4.5 installed and have since uninstalled it, and do not have anything else installed.
Also, it happens to other people with the same source code, and re-installing Visual Studio does not fix the problem. So I have several questions:
Is there any way I can find out what's happening?
I don't understand how the code (the css tag itself) could crash Visual Studio, and am thinking that this is unlikely and it must be something else within my solution, would this be a safe assumption?
Could this have anything to do with installing Office 2010?
Thanks in advance to anyone who has ideas on how to troubleshoot this problem.
Edit:
I didn't find a good answer for this question, but found that installing Visual Studio 2010 and using it instead of Visual Studio 2008 fixed the problem. I have marked the answer below as right as it gave me an idea on where to start looking.
So from this I am going to conclude that this is some sort of Visual Studio bug, but would be happy to see more information if any one else encounters this problem or can shed any light on it!
The above should work - I actually used the solution here - repair office 2010 web authoring components - http://www.ariankulp.com/archive/2010/03/02/web-form-designer-lockup-in-visual-studio-2008.aspx
MSDN Code Gallery shows 45 items tagged Visual Studio 2008 and hotfix. it's very hard to search for your problem with keywords, but browsing through the 45 might help.
I just ran into a similar problem (VS2008 freezing every time I tried to open the Manage Styles / Apply Styles / CSS Properties windows).
What fixed it for me was:
Uninstall Microsoft Visual Studio
Web Authoring Component
Reinstall
Microsoft Visual Studio Web
Authoring Component from the VS DVD
(just run
WCU\WebDesignerCore\WebDesignerCore.Exe; it doesn't have a UI, so you just have to wait for it to finish).

Visual Studio 2008 bugs?

I've touched on these issues before, but that was using a system with vs 2005, 2008, vwd, and 2-3 years of associated junk on ;)
Now I'm running a fresh install of Visual Studio 2008, on Vista. I still have some very annoying issues.
The first, is that when creating a new asp.net site, and a default blank page - it won't run. I get a compiler error, the only way I know to fix it is to add a 'codefile' reference to the top of the aspx page. I need to do this for every page - why??
Secondly, I have an issue in that sometimes when opening an aspx page - it basically wont! A new tab is created, but the window inside the tab is not refreshed, it shows the contents of the previous tab (although the design/split/source bar appears at the bottom) - it's as if just that window has crashed.. I can easily go back to the other tabs, but there's no way of seeing the aspx of that file. The file isn't corrupt in any way, and it seems temperamental - but often occuring on old 2005 projects.
Anyone else experienced this behaviour??
cheers :D
Have you installed Visual Studio 2008 Service Pack 1? It fixes several bugs and adds some new features.
Also install the hotfix rollup package for ASP.NET 2.0: April 2009
It fixes a lot of asp.net related bugs.

Resources