The following expression could not be parsed because of a syntax error or because it uses an undefined namespace prefix or unsupported

The following expression could not be parsed because of a syntax error or because it uses an undefined namespace prefix or unsupported

Problem:

The following error occurs when you try to upload a browser based InfoPath 2007 Form which has .NET “code behind”

Form Verification Status

Failure

The following expression could not be parsed because of a syntax error or because it uses an undefined namespace prefix or unsupported function: /dfs:myFields/dfs:dataFields/tns:SetValue/s1:fd

manifest.xsf

Cause:

For now, it seems that you have built one web service that uses a lot of different complex types ( which have different namespaces ) as a messages to serve different InfoPath forms

Solution:

In short – Just like the joke goes “close everything and re-open”, well it worked for me – or in other words :

1. Remove the Data Connection to the “Set” [WebMethod]
2. Save the form
3. Re-open it
4. Add a new Data Connection to the “Set” [WebMethod]
5. .. and walla ;)

and now you’d get this

The ohh so needed “my” namespace instead of “s1” , “s2” , “s3” …. namespaces

InfoPath 2007 Solution Center

In short, this is a new link

InfoPath 2007 Solution Center

That you should add to this one - InfoPath 2007 in MSDN which one of it’s subfolders is Visual How Tos

ESB Guidance 2.0 CTP2 -January 2009

ESB Guidance 2.0 CTP2 -January 2009

When do you know something is important ? yes , when there’s a development team blog ;)
ESB Guidance Team Blog

Not only that, but we all know that the Microsoft ESB Guidance - Part of Microsoft patterns and practices

And now for the main course – yes , there’s a new ESB Guidance 2.0 CTP2 -January 2009. So after the glimpse we got from the ESB Guidance 2.0 CTP October 2008, I guess this version would be much more stable

January 2009 CTP of the Windows Azure Tools and SDK released

January 2009 CTP of the Windows Azure Tools and SDK released

There was a large crowd in Juval Lowy’s User Group presentation - Special User's Group meeting: Juval Lowy in Israel January 2009 - Introducing the .NET Service Bus. One of the cool things is the fact that he showed is the context and usage of Azure for the regular programmer as well as for architects. That said you should know that a new version of the Windows Azure Tools and SDK CTP of the was announced

In this release both the Windows Azure Tools & the SDK was updated

• Windows Azure Tools for Microsoft Visual Studio
• Windows Azure SDK

What's hot in the new refresh?

1. The problem with VS hanging when you hit F5, this is a huge fix.
2. Fix regarding the limitation of using special characters in entities, which affected some update or delete operations.
3. There have also been a bunch of performance fixes, so the overall user experience feels a lot nicer compared to the PDC release.

p.s. I don’t know about you , but I already bought the yuval’s new book as an eBook version

Professional Microsoft SharePoint 2007 Development Using Microsoft Silverlight 2

Professional Microsoft SharePoint 2007 Development Using Microsoft Silverlight 2

The fact that Israel has now 3 (!) Regional Directors for SharePoint ( the only product that has reach this quantity ! ) Only show that :

1. SharePoint is gaining popularity & widespread
2. SharePoint is a very stable program which can be customized and developed upon very easily :)

On the other hand we’ve all seen the First Look: Office 14 for Web webcast from channel9 – which one of the new features is a Silverlight based edition of Office ;)

Point is, as you can do the math, the next SharePoint, just like BizTalk (*), will have great support for Silverlight built in from the “simple first level webpart” to the “high level of complete LOB Application”.

Now we all know about the Silverlight Blueprint for SharePoint (RTM), which was Nov 28 2008, but did we start diging into these stuff ? no ? there’s a complete set of samples, recently updated are:

1. Hello World
2. Slider Control
3. Colleague Viewer
4. Custom Navigation

More about the blueprints here: http://www.codeplex.com/SL4SP.

Now that said, you should know of a new book - Professional Microsoft SharePoint 2007 Development Using Microsoft Silverlight 2 (Paperback), from wrox, this way you can cover two great technologies : SharePoint & Silverlight

If all of this is too far ahead for you, you can also go to MSSharePointDeveloper.com launched! - "Do Less. Get More. Develop on SharePoint." , Webcast Series: SharePoint for Developers , Moss 2007 and Designer Webcast How-To is growing & WSS 3.0 For the people for additional SharePoint development resources—including Silverlight and SharePoint labs and content

* The comparison to BizTalk is due to the fact that the “current” version of BizTalk, BizTalk 2009, does not host a WF Wrokflow as it does it’s “native/original” Orchestrations  - That’s why we have Dublin :)

Get PublicKeyToken in Visual Studio 2008

Probelm:

The common way we all get the PublicKeyToken is of the Libarary DLL is to Drag and Drop it to the GAC (c:\windows\assembly) folder , and then right click the DLL.
“So ? Where is the problem ?” , you might ask
Well there are two of them:

1. if you’re in Vista , you just might come across a “privileges” problem, which means: you are part of the Administrator Group but you still can’t drag and drop to the Assembly, is there a workaround to get the PublicKeyToken ?
2. If this is “just a step / stage” in the global development , you need to remove the DLL from the GAC , else the project will use the GAC version and not the “development” version – which means you don’t really want it in the GAC , you just need the "Token”

Solution:

In the PostBuild Code add the following

"C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\Bin\sn.exe" -T  "$(TargetPath)"

SSIS on Excel 2007 Data Import & Moss2007 :"Excel Source Output" . The column status returned was: "Text was truncated or one or more characters had no match in the target code page."

SSIS on Excel 2007 Data Import & Moss2007

One of the crucial stages in moving managers from the “Simple all I want I get from Excel” to a more centralized platform like Sharepoint is moving their data !

Well lately not only have I been a :

• “HTML”
• “SharePoint Designer 2007”
• “Adobe Photoshop CS2” & “Paint.Net” Graphics
• “General Specific Site Collection Moss2007 Admin”
• “InfoPath 2007 Browser Compatible Developer” (including InfoPath C# Code)
• “General Web Service & WCF Programmer”
• “Camtasia Studio Video Composer”
• “General Web Part Programmer”
• “Regular T-SQL Stored Procedure Developer”
• “Reporting Services 2005 & 2008 Guru”
• AND (!) “SqlServer2005/2008 Integration Services Package Developer”
• … Not forgetting the every day Project Management meetings, e-mails and all around needed Project Characterization Documents

Like every project manager the first thought is KISS – “Keep It Simple Stupid”. Well, if you’re like me and you know that this is a one time , or close enough, occurrence ( the import of data ) you can do what I did :

1. Open Access2007
2. Import the data from Excel
   
   
   
3. Save the file as Access2003
   
   
   
4. And from there on the SSIS Wizard ( Sql2008 in my case ) will do the work
   
   
   in the process ( in the steps of the wizard ) , you can always check the option to save a local copy of the Package ( without an encryption key ) – your choice :)

for those who still are looking for another solution , a more permanent one that is, here’s a good link

SSIS Excel Data Source: Error with output column “Comments” (5691) on output “Excel Source Output” (5596). The column status returned was: “Text was truncated or one or more characters had no match in the target code page.”

And yes

1. I know SSIS is more my sister’s ( Ella Maschiach's BI Blog ) area , than mine ;)
2. I needed that for an InfoPath2007 form, which always can connect to a Moss List ;)
   
   
   

Try the installation again using a valid copy of the installation package 'sqlncli.msi'

Problem:

If SqlServer 2005 Setup fails and roll back with the following error message:

"An installation package for the product Microsoft SQL Native Client cannot be found. Try the installation again using a valid copy of the installation package 'sqlncli.msi'."

Reason:

It’s probably due to the fact that you have installed .NET Framework 3.5 BEFORE you have installed SqlServer 2005 ;)

Solution:

To work around this problem, uninstall SQL Native Client by using Add or Remove Programs. On a cluster, uninstall SQL Native Client from all nodes. Then, run SQL Server Setup again.