i've installed silverlight toolkit from codeplex (NuGet didn't work, feed was empty.. probably working on the project) and after referencing
Microsoft.Phone.Controls.Toolkit
I get the error :
The type or namespace name 'Toolkit' does not exist in the namespace
'Microsoft.Phone.Controls' (are you missing an assembly reference?)
What could it be?
Because your xmlns is calling it toolbox but the prefix is toolkit.
Change
xmlns:toolbox="clr-namespace:Microsoft.Phone.Controls;assembly=Microsoft.Phone.Controls.Toolkit"
to
xmlns:toolkit="clr-namespace:Microsoft.Phone.Controls;assembly=Microsoft.Phone.Controls.Toolkit"
Or, change your prefix to toolbox. It doesn't matter what you call it; it just has to be consistent.
In this line you declare toolbox as a name to reference the toolkit
xmlns:toolbox="clr-namespace:Microsoft.Phone.Controls;assembly=Microsoft.Phone.Controls.Toolkit"
In this line you reference to the name toolkit
<toolkit:DatePicker Header="Date" Value="9/16/2010" ValueChanged="DatePickerValueChanged"/>
It does not work because those names should be equal. So either declare xmlns:toolkit or reference toolbox:DatePicker
Good luck!
Related
I'm new to Visual C++. I have two separate projects (let's call the first Converter and the second TreeGridView). I have this line of code in the Converter project:
private: AdvancedDataGridView::TreeGridView^ treeGridView;
which throws this error on 'AdvancedDataGridView':
name followed by '::' must be a class or namespace name
I think I understand the error - Visual C++ can't find a class or namespace called 'AdvancedDataGridView' right?
I have a separate Visual Studio project called TreeGridView which has 3 C# projects included in it. One of the projects has an assembly name of 'ExpandableGridView' and a default namespace of 'AdvancedDataGridView' and an output of type Class Library. Another project has an assembly name of AdvancedDataGridView and a default namespace of AdvancedDataGridView and an output type of Windows Application.
Being new to Visual C++ and the codebase I'm using, I'm not sure how to make the error go away. The TreeGridView project (the one with 3 c# projects) does generate an ExpandableGridView.dll file which I've added a reference to in my Converter project, but the error persists. Intellisense doesn't find AdvancedDataGridView at all. Any ideas?
Additional info: When adding the ExpandableGridView.dll as a reference, I get a yellow warning triangle icon on the reference and 'Full Path' in the properties says
The "Microsoft.VisualStudio.ProjectSystem.References.UnresolvedAssemblyReference" reference
could not be resolved.
Solved. I had two references to the same ExpandableGridView dll file - got rid of both of them, then added the latest dll again - after that the error and warning I mentioned above went away.
You're trying to XOR a type with a variable? Pointers are declared using type*, not type^.
See http://www.cplusplus.com/doc/tutorial/pointers/ for a tutorial on C and C++ pointers.
I have successfully installed DNN 8 and all configuration.
i am also referring video to develop module in visual studio.
https://www.youtube.com/watch?v=AKCYRPuoXF4
when i am trying to build the project then
error comes like:
Error 17 The type or namespace name 'DotNetNuke' could not be found
(are you missing a using directive or an assembly
reference?) C:\websites\dnndev.me\DesktopModules\MyDNNModule\MyDNNModuleModuleSettingsBase.cs 13 7 MyDNNModule
Please help to solve that.
thank you in advance.
Working with DNN8, sometimes I get a set of errors with message
The type or namespace name 'DotNetNuke' could not be found (are you
missing a using directive or an assembly reference?)
, probably 10 or 15 of them, and all located on top of one ascx file. (My dotnetnuke.dll is correctly placed in DNN's bin folder). Taking a better look (scroll down!), I can see that - except them - there are some more error messages (maybe just one of them), and that those additional errors are perfectly clear and logical. So I correct my source code in order to avoid those additional messages, and when I do that - those problematic messages also disappear!
In my case it took me a while to find the solution to this problem, since it only got triggered when I made a change to the View.ascx file.
You need the Visual Studio project to target framework to 4.5 instead of 4.5.1.
I got this solution from here.
Make sure to add a Reference to dotnetnuke.dll in the c:\websites\dnndev.me\bin folder
I honestly haven't done anything with DNN 8 CTP yet, I would stick with 7.4.1 until 8 is official released.
I referenced System.Xml in my code, but XmlDocument still does not show up. Whenever I try to use it, it tells me:
Error: The type or namespace name 'XmlDocument' could not be found (are you missing a
using directive or an assembly reference?)
I saw this link that seemed pretty helpful; unfortunately, I am using a Windows Apps template, and it does not allow me to remove or add references, and I am sure that I am not using Silverlight. I am using Visual Studio 2013, with .NET 4.5. Any help is appreciated.
Edit: I am trying to make a background task. This is how I am using it:
XmlDocument toastXml = ToastNotificationManager.GetTemplateContent(toastTemplate);
I got it: the library had been changed or something, so XmlDocument is no longer under System.Xml.
It is now under Windows.Data.Xml.Dom.
This worked:
using Windows.Data.Xml.Dom;
I am facing unknown problem while using Prism 4. We implement business solution in MVVM pattern. For that I have used
1. Microsoft.Expression.Interactions
2. System.Windows.Interactivity
3. GalaSoft.MvvmLight.Extras.WPF4
for Interaction.Triggers, CallMethodAction and EventToCommand.
<SWI:Interaction.Triggers>
<SWI:EventTrigger SourceObject="{Binding ElementName=txtName}" EventName="GotFocus">
<MEI:CallMethodAction TargetObject="{Binding Path=DataContext,ElementName=txtName}" MethodName="txtName_GotFocus"></MEI:CallMethodAction>
</SWI:EventTrigger>
<SWI:EventTrigger SourceObject="{Binding ElementName=txtName}" EventName="KeyUp">
<GMEWCMD:EventToCommand Command="{Binding Path=DataContext.cmdtxtNameKeyUpEvent,ElementName=txtName}" PassEventArgsToCommand="True">
</GMEWCMD:EventToCommand>
</SWI:EventTrigger>
</SWI:Interaction.Triggers>
Everything is working fine but now we required to make whole system loosely couple we choose prism 4. We already achieved this but above code create following problem as below.
Could not load file or assembly 'Microsoft.Expression.Interactions, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
If I comment above code everything is working fine. I don't know what an issue. Does PRISM 4 not support above assemblies?
Please help us to get rid from this problem.
Thank you
This commonly happens to me when I reference both Microsoft.Expression.Interactions and System.Windows.Interactivity in a view that belongs to a module, but I fail to also add those references to the project that acts as the shell.
I had a similar problem with Prism in Visual Studio 2012. The XAML editor would fail with the same exception.
The solution was to install Microsoft Expression Blend SDK. The assembly should be part of SDK. Allegedly, it is necessary for binding between control events and commands in XAML and some code may require it.
I had the same problem during a Prism 6.1 composite app using .NET 4.5.2, where i was referencing in one of the modules (class library) the Microsoft.Expression.Interactions & System.Windows.Interactivity.
Eventually i had to reference the same dlls in the Desktop project (where bootstrapper and Shell belong)
Hello
I try to use PcapDotNet dll but I can't add reference to my project.
It doesn't matter which dll it is. PcapDotNet.Core.dll, PcapDotNet.Base.dll etc.
I have yellow exclamation mark near this reference and can't use any methods from this dll.
Ofc "using PcapDotNet.Core;" is underlined too and compiler shows me: "The type or namespace name 'Core' does not exist in the namespace 'PcapDotNet' (are you missing an assembly reference?)"
Different dll I can add normally.
Any ideas?
I rubbed my crystal ball and it said: "you downloaded this from the Codeplex site and you are using a Visual Studio edition earlier than 2010."
It's usually pretty reliable when it gets that explicit, I'll work from the assumption that it is accurate. If you are not ready to upgrade to VS2010 then you'll need the 0.6.0 version, as documented on the landing page. The 0.6.0 download is listed in the upper right box, this is the link.