Answered by:
Custom XSLT path in Map

Question
-
Hi
i created a XSLT for mapping and gave the custom xslt path property as the path of folder where
it is located and working fine in test map
can i add that property value as link to follow a common structure like(..//..//xslt.xsl)
expert advise please
regards,
Vineeth
Monday, September 30, 2013 9:19 AM
Answers
-
Hi Vineeth,
In “custom XSLT path” in map, is your question about giving a virtual path (instead of physical path) for the XLST like “(../../XSLTName.XSLT”) to let map find its XSLT in different environments?
If you give your path as “/XSLTName.xsl” (i.e. with just a slash-/) , then it points to root of the c: drive. I think this is root of your installation drive and C-Drive is the installation drive in my case. So if you give the path as “/Test/ XSLTName.xsl”, then visual studio would look for the file in “C:\Test\MSDNMap.xsl”. I don’t think it’s documented anywhere; I just tried it at my dev machine.
If your question is about giving a virtual path for XSLT in deployment, then as la Cour mentioned, XSLT will be compiled into the BizTalk .dll, so you cannot point to a common XSLT path.
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful.
- Marked as answer by Vineeth V.L Tuesday, October 1, 2013 5:55 AM
Monday, September 30, 2013 10:18 AM -
Hi Vineeth,
XSLT is complied as part of *.dll in which map (*.btm) file is build/complied. XSLT file is not compiled as physical file.
When you deploy the msi which contain the map and its related XSLT files, its all complied as part of *.dll file. You don’t need to create any folder structure.
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful.
- Proposed as answer by Maheshkumar S Tiwari Monday, September 30, 2013 1:25 PM
- Marked as answer by Vineeth V.L Tuesday, October 1, 2013 5:55 AM
Monday, September 30, 2013 1:05 PM -
The .xsl is treated like any other source code file and is compiled into the assembly at build time. It's like referencing a resource file and does not exist on it's own except as part of the project.
If you export a .msi, it comes as part of it's assembly.
- Marked as answer by Vineeth V.L Tuesday, October 1, 2013 5:55 AM
Monday, September 30, 2013 1:09 PMModerator
All replies
-
The XSLT will be compiled into the BizTalk .dll, so you cannot point to a common XSLT file that can be changed dynamically once the .dll is deployed, if that is what you are asking?
Morten la Cour
- Proposed as answer by .NetNoob Monday, September 30, 2013 12:21 PM
Monday, September 30, 2013 9:25 AM -
Hi,
(..//..//filename.xsl) as per your naming conventions of business .
actually what your are asking?
Thanks
- Edited by anilraos Monday, September 30, 2013 9:29 AM dd
Monday, September 30, 2013 9:27 AM -
Hi Vineeth,
In “custom XSLT path” in map, is your question about giving a virtual path (instead of physical path) for the XLST like “(../../XSLTName.XSLT”) to let map find its XSLT in different environments?
If you give your path as “/XSLTName.xsl” (i.e. with just a slash-/) , then it points to root of the c: drive. I think this is root of your installation drive and C-Drive is the installation drive in my case. So if you give the path as “/Test/ XSLTName.xsl”, then visual studio would look for the file in “C:\Test\MSDNMap.xsl”. I don’t think it’s documented anywhere; I just tried it at my dev machine.
If your question is about giving a virtual path for XSLT in deployment, then as la Cour mentioned, XSLT will be compiled into the BizTalk .dll, so you cannot point to a common XSLT path.
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful.
- Marked as answer by Vineeth V.L Tuesday, October 1, 2013 5:55 AM
Monday, September 30, 2013 10:18 AM -
XSLT is mainly used in xml documentation to give the best look like css give the best look in html format. as you know the tag in xml is not W3c defined but they are arranged according to user mean purely on Document Type definition.Here main type is the processing string <?xml version="1.0"?> and these are defined under this.As you customize tag under the surveillance of DTD, in the same way you customize the xslt. Xslt take place into the namespace.
- Edited by William Keats Monday, September 30, 2013 10:51 AM
Monday, September 30, 2013 10:50 AM -
Hi ashwaniprabhu,
my question is exctly regarding different environment
just for calrification
if in my dev machine i am browsing the xslt from 1 folder and deployed it
in another environment if that msi is using do i need to create the same folder structure and keep the xslt in that folder??
Monday, September 30, 2013 12:56 PM -
Hi Vineeth,
XSLT is complied as part of *.dll in which map (*.btm) file is build/complied. XSLT file is not compiled as physical file.
When you deploy the msi which contain the map and its related XSLT files, its all complied as part of *.dll file. You don’t need to create any folder structure.
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful.
- Proposed as answer by Maheshkumar S Tiwari Monday, September 30, 2013 1:25 PM
- Marked as answer by Vineeth V.L Tuesday, October 1, 2013 5:55 AM
Monday, September 30, 2013 1:05 PM -
The .xsl is treated like any other source code file and is compiled into the assembly at build time. It's like referencing a resource file and does not exist on it's own except as part of the project.
If you export a .msi, it comes as part of it's assembly.
- Marked as answer by Vineeth V.L Tuesday, October 1, 2013 5:55 AM
Monday, September 30, 2013 1:09 PMModerator