MVCAwesome, MVC4 and NuGet - asp.net-mvc-4

I created a new MVC4 project using Razor syntax, and used NuGet to add MVCAwesome.
Looking at this page, it appears that all the expected files and configuration files appear to be in place. I made the edit to the Views/Web.config as directed.
When I try to reference any Awe() controls however, the reference to Awe() shows up in red text, and I get an error message: Cannot resolve symbol Awe()
#Html.Awe().DatePickerFor(model => model.BirthDate).ChangeMonth(true).ChangeYear(true)
Has anyone gotten this to work? What am I missing?

Just FYI, I was able to contact the maintainer of this library. It turns out that in this newer, NuGet version of the controls, you don't need the Awe() part.
For some reason, DatePickerFor still seems to be missing, but I do see other controls there from the package.

Related

Error adding WrapPanel

I created a new blank Windows 10 Universal app and tried to add a WrapPanel exactly as per the sample code in the link: WrapPanel XAML Control
I am getting the following error message on wrapPanel:WrapPanel
The name "WrapPanel" does not exist in the namespace "using:Microsoft.Toolkit.Uwp.UI.Controls.WrapPanel"
I have already added xmlns:wrapPanel="using:Microsoft.Toolkit.Uwp.UI.Controls.WrapPanel" as per sample code.
Full code and errors (please click image for better quality):
I have tried to Clean and Build/Rebuild but it doesn't help. I also made sure that I am targeting the latest Windows 10 version:
Please help!
Update: I tried using xmlns:wrapPanel="using:Microsoft.Toolkit.Uwp.UI.Controls"
as suggested but I still get this error. Again, I tried clean and build/rebuild and am getting the a similar error:
The documentation has a typo. The WrapPanel control is not in the Microsoft.Toolkit.Uwp.UI.Controls.WrapPanel namespace, but rather just in Microsoft.Toolkit.Uwp.UI.Controls, so use the following
xmlns:wrapPanel="using:Microsoft.Toolkit.Uwp.UI.Controls"
And it should work as expected. I will push an update for the docs.

LNK2019 using QQuickWidget

Quite a strange error just as the image above.
I just drag a QQuickWidget in then I got this Link error.Everything went well again after I delete that QQuickWidget.
A QT protosomatic class will be included automatically isn't it? Or I have to do something like add a dll dependency like what must be done when using VS? If so then how to do so in QT5?
Or maybe it's caused by some missing dlls?
Thanks for answering.
ps: I'm using QT5.5.0

how to set "infragistics" carousel panel reference?

Which reference has xamcarouselpanel?
When I build my project I get an error that igwindows:XamCarouselPanel was not found. My code is:
igwindows:="http://infraistics.com/Windows"
and the error occur in:
igwindows:xamcarouselpanel.ViewSetting
If anyone has a link to this dll please attach it in the answer.
First of all you should write
xmlns:igwindows="http://infragistics.com/Windows"
in xaml in order to add a namespace and you should have corresponding reference in your project.
After you installed the Infragistics on your computer you should add InfragisticsWPF.XX.X reference.

MVC3 Razor View Project using VB.NET gives Syntax error in Error List window for all vbhtml pages

Using MVC3 and Razor View engine, I created a VB.NET web application in VS 2010. This creates the default Account and Home Controller along with corresponding Action Views.
Now if I open any vbhtml file I get the following error message in the Error List window.
Error 50 Syntax error. C:****\MVC3AppVB\Views\Account\LogOn.vbhtml MVC3AppVB
(See screenshot here http://www.flickr.com/photos/7672540#N07/5469248676/)
Who ever this app compiles and runs without any problem. I tried to create the same project using C# and there is no error message in the Error List Window.
Can anyone explain why this error message shows up only for VB and not for C#?
Thanks in advance.
The problem is with MVC3 and webpage 1.0 tooling. This issue has been answered in codeplex.
Probably some bug with the Intellisense. Try recompiling the project. Unfortunately the Razor Intellisense is far from perfect. I hope it will be improved in future releases of Razor.

"The tag 'MenuItem' does not exist in XML namespace 'clr-namespace:System.Windows.Controls;assembly=System.Windows.Controls.Input.Toolkit'" error

I'm getting an error trying to build a Silverlight application on a new machine. (Silverlight 4, Visual Studio 2010) This application compiles without error on four other machines.
The error is:
the tag 'MenuItem' does not exist in XML namespace 'clr-namespace:System.Windows.Controls;assembly=System.Windows.Controls.Input.Toolkit'.
The references appear to be pointer to the correct assemblies. Has anyone else ever had this problem?
Another reason this issue may occur is due to missing a reference to all "three" assemblies required to use the portions of the the Toolkit controls.
Make sure you have reference to the following assemblies if attempting to use the Toolkit inputs (and assuming the themes also possibly).
System.Windows.Controls
System.Windows.Controls.Toolkit
System.Windows.Controls.Input.Toolkit
This solved the problem I was having in relation to the error.
http://marktinderholt.wordpress.com/2011/07/12/silverlight-toolkit-for-silverlight-5-beta
its the recompiled toolkit in SL5, just reference those and you're set
You can always fall back on creating the context menu in code.
public LedgerEntryControl()
{
InitializeComponent();
ContextMenu contextMenu = new ContextMenu();
MenuItem voidMenuItem = new MenuItem() { Header = "Void" };
voidMenuItem.SetBinding(MenuItem.CommandProperty, new Binding("Void"));
contextMenu.Items.Add(voidMenuItem);
ContextMenuService.SetContextMenu(this, contextMenu);
}
looks like you're missing the Silverlight Toolkit on that machine, but it's installed on the four other ones.
For some reason, the SilverLight Toolkit from NuGet Package Manager is for SL4, even when the project is set to SL5. You can download the SL5 version directly from CodePlex. Note that the date is December 2011, instead of February 2011 like the SL4 version.
If for some reason the MSI does not install (which happened to me), you can extract the files contained in the MSI using 7-zip. All I had to do was manually add a reference to System.Windows.Controls.Input.Toolkit.dll from the extracted files, and my SL5 project now compiles successfully with its NumericUpDown control. Happily, my program now compiles both in Release and Debug mode.
Also to add, for those who have not already done so, you may need to have a reference in the XAML to the correct toolkit. I used the following:
<sdk:Page xmlns:input="clr-namespace:System.Windows.Controls;assembly=System.Windows.Controls.Input.Toolkit" ... >
Note that the first part, where is says input, is what needs to be typed in the XAML to use the control:
<input:NumericUpDown x:Name="myControl" ... />