tsackey's Profile
Reputation: 2
Apprentice
- Group:
- Members
- Active Posts:
- 48 (0.04 per day)
- Joined:
- 11-March 10
- Profile Views:
- 2,491
- Last Active:
May 03 2013 01:17 PM- Currently:
- Offline
Previous Fields
- Country:
- Who Cares
- OS Preference:
- Windows
- Favorite Browser:
- FireFox
- Favorite Processor:
- Intel
- Favorite Gaming Platform:
- PC
- Your Car:
- Who Cares
- Dream Kudos:
- 0
Posts I've Made
-
In Topic: Can't reference an assembly in Xaml
Posted 9 Apr 2012
Not sure either, the only thing i can think of is i renamed my namespace or my class name(can't remember now since i did it over the weekend while drinking...) and this might not have updated all the way. This is what the xaml looks like now
xmlns:myControl="clr-namespace:CalendarControl;assembly=ExtendedCalender"
instead of
xmlns:myControl="clr-namespace:CalendarControl;assembly=CalendarControl"
The renaming was done after i added the reference so, i removed the reference and re-added it but still didn't worked. Maybe that's my problem but anyway thanks again. -
In Topic: Can't reference an assembly in Xaml
Posted 9 Apr 2012
Am using 4.0 -
In Topic: Can't reference an assembly in Xaml
Posted 9 Apr 2012
eclipsed4utoo, on 09 April 2012 - 11:00 AM, said:Hmm....I had no problems adding a Custom Control project(called CalendarControl) to a solution, adding a Custom Control to the project, inheriting from Calendar, building, adding a reference from the UI project to the DLL of the custom control project, adding the XMLNS, and adding the control to the form.
Now when I added the XMLNS, it gave me this when choosing it from IntelliSense...
xmlns:myControls="clr-namespace:CalendarControl;assembly=CalendarControl"
So, i picked the actual dll generated in the debug folder of my custom control instead of the one presented in the projects tab when adding a reference and that fixed my issue. Pretty dumb... but what is that dll in the projects folder for then? Thanks very much for you help -
In Topic: Can't reference an assembly in Xaml
Posted 9 Apr 2012
eclipsed4utoo, on 09 April 2012 - 10:50 AM, said:Quote
Also i thought you always had to specify the assembly name in xaml?
I guess if the assembly and namespace are the same, you only have to give the namespace. Maybe something the VS does for you.
Let me set this up and see if it happens for me also.
Thanks, let me know if you need anything else especially in the custom control project. -
In Topic: Can't reference an assembly in Xaml
Posted 9 Apr 2012
eclipsed4utoo, on 09 April 2012 - 10:32 AM, said:When the IntelliSense shows up, is your CalendarControl assembly in the list? If so, choose it directly instead of trying to type the information in. Then do a rebuild of the project.
I did that and that gets rid of one error (the one in the xmlns) but i still can't instantiate a my ExtendedCalendar class. This is what it looks like now.
<Window x:Class="WpfApplication1.MainWindow" xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" xmlns:myControl="clr-namespace:CalendarControl" Title="MainWindow" Height="350" Width="525"> <Grid Name="myGrid"> <myControl:ExtendedCalendar name="calendar"></myControl:ExtendedCalendar> </Grid> </Window>
The error is on line 7, it's acting like my class is not in that namespace. Below is my class
using System; using System.Windows.Shapes; using System.ComponentModel; namespace CalendarControl { /// <summary> /// /// </summary> public class ExtendedCalendar : Calendar { } }
Also i thought you always had to specify the assembly name in xaml?
My Information
- Member Title:
- New D.I.C Head
- Age:
- Age Unknown
- Birthday:
- Birthday Unknown
- Gender:
-
- Location:
- Does it matter
- Years Programming:
- 2
- Programming Languages:
-
Java
C++
C#
Contact Information
- E-mail:
- Private
Friends
|
|


Find Topics
Find Posts
View Reputation Given



|
Comments
tsackey has no profile comments yet. Why not say hello?