DISK = ‘C:\DB.BAK
RESTORE DATABASE DBLogicalName
FROM DISK = ‘C:\DB.BAK’WITH
MOVE ‘YourMDFLogicalName’TO ‘D:DataYourMDFFile.mdf’,
MOVE ‘YourLDFLogicalName’ TO ‘D:DataYourLDFFile.ldf’
got it from the following link :
call templates: this is similar to a function call
apply templates: finds a specific pattern and apply s the template.
XML document or XML Node is not serailizable.
so the rule of thumb in biztalk is that only serlizable types can be used in orchestrations with long running types and if you require to non serailizable type use them within a Atomic scope.
Now comes the interesting part xmldocument and xmlnode : if you create variable of type xmlnode , you will come across the following exception:
a non-serializable object type ‘System.Xml.XmlNode varXmlNode’ can only be declared within an atomic scope or service
but if you create a xmldocument variable the above error is no thrown why? BizTalk engine by default serailizes xmldocument….
it installs a activeX and tells you if you computer supports a game or not.
IT is changing fast, we have a new technology being introduced every day….. sometime it can be very difficult to keep up with this everlasting changes.
My advice is don’t get bogged down, as long as you are good in OOPS you will catch up in no time why ?
Because every new technology contains classes, interfaces and design patterns so as long as you are good with the core concepts in oops and the language fundamentals you should be good.
Remember you are learning only these new ideas and there implementation (which have used oops).
we had a requirement where we had to search for text in table which stored html content, started with writing a custom library did not make much progress, googled and then found this amazing tool html agility pack which does the conversion like a charm…
In order to answer this question first we need to understand the following WSDL styles:
1) RPC : Operation oriented say ex: InsertStudent, <soap:body> element should contain the name of the method that is being invoked </soap:body
2) Document: is data oriented <soap:body> does not care what is being passed in the soap body </soap:body, this style came into the picture because of the limitations of RPC style where schema validation was difficult, included the type information and don not conform to WSI and etc..
Extensions for the above
3)Document/Literal: Microsoft proposed this standard where the soap body element will contain the web method name.
Now imagine a wsdl having the same name in WCF, we can’t because by default all the WCF services conform to the document literal standard where the soap body should include the method name , so this why we cannot have method overloading (same method name but different parameters) in WCF.