Develop Reference

RDLC ReportViewer control error with VS2022 WPF [duplicate]

Hi I've created a new solution on .net 6 on VS2022 , and now I need to create reports but it looks like there is no way in vs2022. is there a way to use reporting services RDLC files in WPF on VS2002 ?
Mean a while I've open the solution on VS2009 in order to use it for building RDLC reports, but when I try to associate the data source to an Object I got this error
My object is a Class in a referenced project (class library .net6) the class is:
public class prueba
{
public int MyProperty { get; set; }
public int prop2 { get; set; }
public int prop3 { get; set; }
}

There is now a RDLC Report Designer Add-In for Visual Studio 2022.
To use those reports in your application, you need an RDLC renderer (aka "Microsoft ReportViewer"), which is available for .NET 4.0-4.8 as a nuget package:
Microsoft.ReportingServices.ReportViewerControl.Winforms
Microsoft.ReportingServices.ReportViewerControl.WebForms
Do note, though, that Microsoft did not release a ReportViewer for .NET Core or .NET 5+, and they have announced that do not intend to release one in the future (see, for example, the comments on this blog post).
There are some enthusiast ports/recompilations floating around on github and nuget, but they are not from Microsoft, nor has Microsoft given them permission to do that, so using those packages carries a certain amount of technical and legal risk. That's not something you want to do in a commercial project.

You only can use projects with netstandard, 2.0 or 2.1
so the class you will use as a data source only can be in a project using .NetFramework or netstandard.

How do you add schema annotations for EF Core in a Portable Class Library

For a project I am working on we have written a Portable PCL to contain models and other code that will be shared between multiple projects. The Data Access Layer is in another project in the solution, but I would like to use EF data annotations in the PCL to match our current convention. I have data annotations in the System.ComponentModel.DataAnnotations namespace working just fine, but System.ComponentModel.DataAnnotations.Schema annotations are not found.
The reference is added, and I have even tried re-adding EF to the PCL, but I haven't had any luck. I read another post where they ran into an issue using both namespaces simultaneously, but I can't even get .Schema working by itself.
Here is an example of what my code looks like:
using Newtonsoft.Json;
using System;
using System.Collections.Generic;
using System.ComponentModel.DataAnnotations;
using System.ComponentModel.DataAnnotations.Schema; //VS shows that this is not being used
namespace Shared.Models.User
{
public class BaseUser
{
[JsonProperty("id")]
[Key]
[Column("UserId", Order = 1)] // ***ColumnAttribute not found 
public Guid Id { get; set; }
...
[JsonProperty("fullName")]
[NotMapped] // ***NotMappedAttribute not found
public string FullName => String.Format("{0} {1}", FirstName, LastName);
...
}
}
The PCL is targeting .Net 4.5, .Net Core 1.0, UWP, and Xamarin platforms. In the Nuget Package manager it shows that both of the before-mentioned namespaces have been added to the project, but they do not show up in the solution explorer. I have tried cleaning the project, building, and restoring packages but still nothing. I don't see any reason that this shouldn't work in a Portable PCL, but am I missing something?

Does installing the System.ComponentModel.Annotations NuGet package help? If not, they may just not be available on that type of project.

DLL References into Application but not Class Library

I am trying to integrate the WeifenLuo.WinformsUI.Docking assembly into my application. To rule out external factors I created a new .Net 4 Winforms app and reference the DLL. Works fine.
I then created a .Net 4 Class Library and referenced the DLL. This this doesn't work and as soon as I try to use anything in that Docking namespace it won't compile.
To recap
C# Exe ---reference--> WeifenLuo.WinFormsUI.Docking.DockPanel.dll // OK
C# Class library ---reference--> WeifenLuo.WinFormsUI.Docking.DockPanel.dll // Not OK
I also have the WeifenLuo source and confirmed it's a class library referencing the same version of .Net. I tried adding a class library in their sample solution and referencing the WinForms project directly (not the result in assembly) and it still isn't linking properly.
Updating with Screenshot

You can't declare a private variable Inside a namespace.
Try the following code
namespace Test
{
public class Class1
{
private WeifenLuo.WinFormsUI.Docking.DockPanel dockPannel;
}
}
And if it still doesn't work, provide the error message.

Is EntityFramework required in my Models project that uses code first attributes to define models?

I created a seperate project and copied over my models to this project.
I referenced
using System.ComponentModel.DataAnnotations
My models are defined like:
public class File
{
[Key]
[Column("file_id")]
public int Id { get; set; }
[Column("user_id")]
public int UserId { get; set; }
...
}
The error I get is:
The type or namespace Column could not be found ...
If I add a reference to EntityFramework it works fine, but I want to re-use my models project by referencing it for my Web Api Rest Client library and don't want to bring in EF for no reason.
I am using .net 4.0
Did they fix this issue (making it loosly coupled with EF) in 4.5?

Yes, this issue is fixed with .NET 4.5.
The Object Catalogue for the EntityFramework.dll of EF 5 with .NET 4.0 (also known as EF 4.4) shows all the attributes in the System.ComponentModel.DataAnnotations and System.ComponentModel.DataAnnotations.Schema namespace that are in the EF assembly:
Whereas the EntityFramework.dll of EF 5 with .NET 4.5 does not contain those namespaces anymore:
The attributes have been moved into the .NET 4.5 framework assembly System.ComponentModel.DataAnnotations.dll under the same namespace they had been before in the EF assembly:
(MinLength and MaxLength are in System.ComponentModel.DataAnnotations as well, the total list of all attributes in there is too long for the screenshot.)

You shouldn't need to reference all of EF. You should just be able to reference System.ComponentModel.DataAnnotations.dll. Adding EF may just add that as a reference for you.
FYI MSDN will tell you which namespace and assembly a framework class exists in.

You don't have to use attributes to create metadata. The whole concept of POCO models is just about it.
The trick is to have an assembly of model classes which do not reference the EF. You can safely reuse this assembly in any context.
Then, in another assembly, you create your DbContext class, refrence the EF and create the metadata programatically. In EF this approach is called Code First Fluent Api.
http://codefirst.codeplex.com/

C# Portable Class Library - How do you include System.Data.Linq

Is it possible to reference the System.Data.Linq in a Portable Class Library project?
Note:
I am just trying to share code between a WP8 and WinStore8 app [DataContext]

No it is not. The Data namespace is unavailable in PCLs.
You can tell because http://msdn.microsoft.com/en-us/library/system.data.aspx none of its members have the PCL icon, and it is not listed on http://msdn.microsoft.com/en-us/library/vstudio/gg597391%28v=vs.100%29.aspx