I added reference and its OK but after build its show like this again
guys help me to fix this things. I really don't know what is happening!!!. my target framework is 4.5.
Related
I have a project which still uses Xceed WPF Toolkit DataGrid, and I want to upgrade it to https://github.com/dotnetprojects/WpfExtendedToolkit.
I have unistalled the Xceed nuget and installed this one: https://www.nuget.org/packages/DotNetProjects.Extended.Wpf.Toolkit/
Once done that, I have removed these two lines from my XAML:
xmlns:xcdg="http://schemas.xceed.com/wpf/xaml/datagrid"
xmlns:xctk="http://schemas.xceed.com/wpf/xaml/toolkit"
And replaced them with these other two ones:
xmlns:xcdg="clr-namespace:Xceed.Wpf.DataGrid;assembly=DotNetProjects.Wpf.Extended.Toolkit"
xmlns:xctk="clr-namespace:Xceed.Wpf.Toolkit;assembly=DotNetProjects.Wpf.Extended.Toolkit"
But it does not work. Both namespaces are not found in the assembly.
Anyone can help me to setup this, please?
Thank you
We have been having troubles with deserializing sql exceptions using newtonsoft.net
Version 11.0.2
On .Net 4.6.2 (Full)
We didn't have these issues before when we where on an earlier version of newtonsoft. (10.x)
Reproduction case in Gist
I have been searching around for how to fix this. But all i can find are solutions in which you decorate the offending property with an attribute. Which obviously is not a option here.
Upgrading our .Net version is an option, but is non trivial for us. So im trying to find out if i have other options. Im not even sure that upgrading the .net version is going to fix this.
Update: I have been looking into using a custom ContractResolver to try and restore the old behavior, as suggested in the comments, however this does not work.
Upgrading to newtonsoft 12.0.3 also does not help.
Upgrading to Net48 also does not help.
Using VS2015, if I create a new blank project, I get missing assembly reference errors, as shown below:
I haven't touched anything from the initial setup. I can't figure out what's wrong?
I needed to run dnu restore as my dnvm versions were out of alignment.
It's something I really struggle with: I get really confused by all the places where a dnx version needs to be set. Wish MS could make it simpler and/or provide a simple guide/explanation.
My goal is to add a reference of my ASP.NET vNext to the old MySql.Data.dll. I think that this should be possible.
I put it in a NuGet package but if I compiled my project, I receive an error message.
Anything there is wrong.
Is there a guideline anywhere showing how to add DLL references? I searched a lot until now, but haven't had found anything.
I assume this is same question as the post below? If you still have questions please do let us know.
http://forums.asp.net/t/1998097.aspx?Add+NET+4+5+Assembly+As+Reference+
One workaround is to create a class library project with your library reference. Then use a project reference from your website to the class library project.
I have a .NET 4 website in VS2010 stored in a TFS 2010 team project. I need to add a reference to System.Data.Linq.dll to the website. I am referencing a LINQ DataContext that is defined in another project and I get build errors saying that I need the reference to System.Data.Linq. I go up to the "Add Reference" menu option and add it like I would any normal reference, and it even shows up in the Web.config and in the Properties pages for the website... BUT if I build I still get the same error.
So I found a place in my code where I was referencing the LINQ count function and it told me it was invalid because I was missing a reference and it offered to add the reference automatically. I told it to add the reference automatically and it is at this point that I get the error mentioned in the subject:
TF14040: The folder $/Folder/Subfolder may not be checked out. No items were checked out
I've done some research online but I haven't been able to find much. I saw on a blog that making the folder not readonly fixed the issue for him, but it didn't seem to work for me unless I misunderstood something.
I tried loading up the project from source control onto a fresh computer where that project had never been loaded before and I can reproduce the issue the same way. Help would be greatly appreciated.
FWIW, this error also occurs in different circumstances. I had the same error today from the command line when trying to use tfs checkout SomeFolder /login:user,password, although this was not within the context of an asp.net app, I'm currently working on dependency replication. For me, adding the /recursive command worked, like this:
tfs checkout SomeFolder /recursive /login:user,password
The hint to try that came from here, by the way.
I have no idea if this is your problem but I've noticed that TFS2010 seems to have some bug somewhere around folder renames/deletes/changes or something. The bugs seem to go away when you check everything in and try again after the folder change has been saved to source control. I have hit this issue a dozen times this week but don't know exactly what the scenarios are. It's quite frustrating.
I figured it out, but it's a little strange. I had some build errors that I hadn't fixed yet, also my web.config file used to be for a 3.5 SP1 site and I upgraded the site to 4.0. Somewhere along the line the build errors and the web.config combined to form this strange weird error that apparently has nothing to do with TFS.
I figured it out by creating a new website and slowly moving over portions of my site to that new site. Things didn't go totally crazy until I moved over my web.config. So I went back and updated my web.config file so that it more closely matched the way a .Net 4 web.config should by trimming out a lot of stuff and now things are good and building fine. Thanks for the help.