Search
Saturday, May 30, 2020 ..:: Blendblog.net ::.. Register  Login
 Bloggers Minimize

  
 Sponsors Minimize

 Print   
 Users Online Minimize
Membership Membership:
Latest New User Latest: ZoeGellert02
New Today New Today: 2
New Yesterday New Yesterday: 0
User Count Overall: 8401

People Online People Online:
Visitors Visitors: 8
Members Members: 0
Total Total: 8

Online Now Online Now:

  
 Welcome to blendblog.net! Minimize

If you are a developer or designer who is creating cutting edge user interface experiences using Microsoft Expression Blend you've just found a great resource!  The purpose of this site is to share our experience with this brand new product.  As with any new piece of software there is a ton to discover.  Bugs will be revealed and workarounds discovered, hopefully this can be a resource to share in the discovery process!

While this site will focus largely on Expression Blend, it will also encompass WPF, Visual Studio, Silverlight, and other .net 3.5 technologies as they relate to the creation of great software.

Please login using your Microsoft LiveID or register a new account.  Doing so will let you comment on any of the blog entries on the site.  We look forward to helping you in your endeavors as well as you helping others in theirs!  We'd love to have more bloggers on our site...if you are interested please register and contact us!

Follow us:


  
 UPDATE!! Issues creating a UserControl as a dll in Expression Blend Minimize
Location: BlogsLarry Tawes - The Blendaholic    
Posted by: Larry Tawes 1/6/2008 10:49 PM

I'm quite happy to find out this issue seems to have been resolved in Expression Blend 2 December Preview!!
====================================================================================================

Narrowing down the problem, this issue only occurs when trying to create a new user control with the language set to Visual Basic.

Steps to reproduce:
1.  Open Expression Blend.
2. Select  New Project.
3. Select WPF Control Library.
4. Set the language to Visual Basic.
5. Click OK.
6. Create a control.
7. Build the project, the user control is created as a .dll in the bin\debug directory for the project.
8.  Create a new WPF application.
9.  Add a reference to the .dll you just created.
10.  Build the project (not really necessary when using a dll, the user control shows up in the Asset Library before building the project).
11.  From your Asset Library select the Custom Controls tab.
12. Select your user control and drag it out on the art board.
13. Build the project and the following error occurs:

Build Error:  The Project could not be built.  Check the results pane for more details.

The tag 'UserControl1 does not exist in XML namespace 'clr-namespace:;assembly=ReleasedControlTest'. Line 10 Position 4."

Interestingly enough, the error does not occur if you set the language to C# in step 4 above when building your user control.

Since we're primarily a VB shop my work around has been to create the WPF user control in Visual Studio first using VB then open and edit the UserControl in Expression Blend.  I posted this issue to the MS Feedback site and a few days later my posting was set to resolved by MS.  I was hoping the latest Blend Service Pack would have the fix in it but no dice.

Permalink |  Trackback

Comments (1)   Add Comment
Re: Issues creating a UserControl as a dll in Expression Blend    By Karl Shifflett on 12/19/2007 3:21 PM
I'm using UserControls in all my VB.NET applications and don't have this problem.<br><br>It might because I'm creating the control library using Visual Studio and then switch back over the Blend. I've noticed that things seem to work better when I create projects using VS and then use Blend for the design.<br><br>Hope this helps,<br><br>Karl<br><br>http://karlshifflett.wordpress.com<br>


Your name:
Title:
Comment:
Add Comment   Cancel 

  
 Search Minimize

  
 Archive Minimize

  
 Blendblog Survey Minimize
Our next client application will be written using:




Which Tablet Do you expect to buy?





Submit Survey  View Results

 Print   
Copyright 2011 by blendblog.net   Terms Of Use  Privacy Statement
DotNetNuke® is copyright 2002-2020 by DotNetNuke Corporation