BizTalk Server: Basics principles of Maps – Introduction to map editor (Part 3)

BizTalk Server: Basics principles of Maps – Introduction to map editor (Part 3)

The map editor, BizTalk Mapper Designer, enables us to perform transformations of complex messages in a visual and extremely simple way, expressed in graphics associations of links that define the relationships between the various elements of messages. These relationships between elements are internally implemented as XSL Transformations (XSLT – Extensible Stylesheet Language Transformation) which is […]
Blog Post by: Sandro Pereira

Publishing an InfoPath form to Sharepoint 2010 for WebBrowser

Publishing an InfoPath form to SharePoint 2010 is not that difficult, that is difficult is getting it published, when it has code behind for the use in the Web Browser.

I recently battled with this, and I must say it’s better than it used to be, making InfoPath VERY powerful, particularly if you can use code behind, and even call your own .net dll’s from the form.

For most they have got somewhere, but have not got it fully working.. if you are one of these people read on.

Do you want to activate it in the site collection, but can’t upload it?

First you need to do this:

1. Open SharePoint 2010 Central Administration.
2. Click General Application Settings.
3. On the General Application Settings page under InfoPath Forms Services, click Upload form template.

You GET: ERROR: This form template has not been published. Open the form in the InfoPath Designer and publish the form to SharePoint using the Administrator-approved form template method in the Publishing Wizard.

Do the following:

Important: Ensure that the security and trust is set to full trust, with a certificate.


1. Publish the form to SharePoint from InfoPath.

2. Note down where you published it: http://msite/template.xsn

3. Go to your web browser and go to this URL, download the PUBLISHED template.xsn

4. SAVE IT locally.

OR

4a. Better way: Publish it to a network location say c:\MyFormTemplates, you do not need it in SharePoint YET.

5. Now upload the {template}.xsn, (Rename if you like) to SharePoint admin.

You should get: The form template has been successfully uploaded to the farm. To make the form template available in a site collection, activate the form template from the Manage Form Templates page or from the feature activation page in the site collection.

6. Now you can activate it in your site collection… etc…

Go to your site where you want to use the form.

Site settings / site collection administration

Site collection features

Look for your Infopath Form Template, (it’s sorted alphabetically)

Press Activate

THE KEY to enabling the form for the browser is in how you set up for form library…

Under Site/{FormLibraryName}/form library settings/ advanced settings.

SAY Allow management of content types = YES

Then hit ok.

Now go down to content types, and defined your content type, say add from existing site content types, which you just activated… You do remember the NAME of the form you uploaded in admin before??

Make sure that it is the default content type, and everything will be good.

Grant permissions to your users, and have them press new document, and up comes your form in the browser…

You can then put your workflow on the form library, or hook BizTalk up to the form Library, and you have full end to end Form and Workflow.

.NET: Microsoft’s new .NET language ’D-flat’ .net

Local MS Developer pillar Andrew Coates spilled the beans on this next new language
to come out of MS Research.

Db.NET or ’D flat’ – F#, C# and the Cinderella of the 3 sisters ’VB.NET’

(Last year I was introduced to F# over a 5 month project and absolutely loved the
simplicity and freshness of it – async was simple, tasks, functions and code that
would normally take 400 lines in C#, we were able to do in 100 in F#)

It promises:

– speed

– optimisation (I wonder if it’ll be smart enough to run tasks on different CPU cores?)

There is a focus on Orchestration – data Orchestration found here http://thenextlanguage.net/a-focus-on-orchestration/

Where it talks about “An example of the close collaboration between the product team
and the company’s research arm is the use of Schenkerian Analysis in
the compiler to maximize orchestration between sections of the code.”

Oooh I thought – let’s check out what this is Schenkerian Analysis and
a quick check of Wikipedia reveals http://en.wikipedia.org/wiki/Schenkerian_analysis

Schenkerian analysis is a method of musical
analysis
of tonal music based on the theories of Heinrich
Schenker
. The goal of a Schenkerian analysis is to interpret the underlying structure
of a tonal work. The theory’s basic tenets can be viewed as a way of defining tonality in
music. A Schenkerian analysis of a passage of music shows hierarchical relationships
among its pitches, and draws conclusions about the structure of the passage from this
hierarchy. The analysis is demonstrated through reductions of the music, using a specialized
symbolic form of musical notation that Schenker devised to demonstrate various prolongational
techniques
. The concept of tonal prolongation, in which certain pitches determine
the goal of other, subordinate pitches, is a cornerstone of the pitch hierarchy that
Schenkerian analysis involves itself with.”

So tones, pitches and music is where this algorithm has its rootsI can see how you
could take this analysis when applied to the frequency of music and apply it to the
frequency of code items; data being hit etc.

I’ll crack open this VS.2011 extension and see what transpires

Grab the TOOLS here – http://thenextlanguage.net/tools/

Blog Post by: Mick Badran