Found my missing message - posted it in the Lounge forum.

Another note:  It is my intention to do the majority of Silverlight 4 Client development in Blend 4.  But after I build and save all in Visual Studio 2010, open the saved solution in Blend 4, and try to build it in Blend 4 (still have not done ANYTHING to the bare template provide by Intersoft) - I get two warnings and one error message.  I'm guessing its something to do with my configuration and not a real bug??

See attached screenshot (paraphrased as follows:)

Warning #1 -  The referenced Silverlight project'..\Intersoft.Silverlight.CSharp.BusinessApp\Intersoft.Silverlight.CSharp.BusinessApp.csproj' does not exist - line 317

Just created a generic Silverlight 4 business application from the Silverlight template (no additional code), did the build, ran debug and successfully registered and logged in, did a save, opened up project in Blend, did a build with no errors, ran debug and successfully logged in - all the same as before installing Intersoft. 

Have also successfully trialed some Intersoft controls, Infragistics, etc. controls in other trials. 

Conclusion appears there is something wrong with the Intersoft template(s)  themselves - (same issue with at least one other template), or through the install, configuration, or whatever.  Intersoft evaluation is now on hold until I can get this resolved somehow. I have tried rebuilding the install several times with no success. 

A clue?  Could the issue be related to the way that Intersoft interacts on initiating a new Intersoft template?

If you initiate a Silverlight template (see attached), you have a choice to select the Name, (folder) Location, Solution Name, but when you initiate an Intersoft template, there is only one (unnamed) option (see attached). This anomoly persists until you cancel and start over to use a different (non-Intersoft) template.  Shouldn't the three fields still need to be filled in with the new information?

I hope this helps

Bruce

Based on my test, if I use the Intersoft ClientUI MVVM Business Application template under Silverlight folder the solution will build successfully in both VS 2010 and Blend 4. However, using the Intersoft ClientUI MVVM Business Application template under Intersoft Solutions / Silverlight does produce some issue.

I have submitted a bug report for this template issue, I am very sorry for the inconvinience caused by this issue. The developer just updated me that issue is caused because the path to the project template is too long so it could cause the issue I am having. Try using the solution provided under Silverlight folder or move the template project location so the path will be shorter.

I also could not replicate the interface in which you could only input the name of the project in VS 2010, in my test creating a new solution will require us to input Name, Location, and Solution Name.

Hi Bruce,

You can actually ignore the missing 'Shell' warning, that's because the Shell key is added at runtime. In Blend, it's showing fine since it's added to DesignTimeResources, a special file that Blend will use to resolve design time resources, but unfortunately, VS 2010 doesn't aware of such design time resources.

Hope this helps,
Jimmy.

This worked for me.  I shortened the path name for the projects template and all now works.  

I would consider this as a work-around to a root cause that still remains.  Why the issue just with Intersoft and not other templates like those provided in visual studio and the silverlight toolkit?

It turns out the the other issue 'could not replicate the interface in which you could only input the name of the project in VS 2010' is a related symptom.  With the shortened path name this anomoly has disappeared as well.

I suspect others will run into the same issue soon enough - maybe a heads-up comment in your installation notes might help a little.

Thanks for your very timely response and help.

Bruce

I have discussed your concern with the developer and it seems the issue cause by visual studio path limitation to 246 character.

We will provide a KB article for this issue for other users who might have the same issue.