Use in .Net Framework Legacy (4.0 to 4.6.1) #223
Replies: 7 comments 2 replies
-
Hi,
We used to support older frameworks. But then some updates to the engine
required the client code to be netstandard compatible.
Now it seems like this limitation is no more.
So you're right we can technically bundle net2 build as well as netstandard
You can submit a pull request, or wait a bit till when I have to look into
it.
Thanks,
Cheers
…On Sun, 17 Sept 2023, 07:15 Erickson Lima, ***@***.***> wrote:
Hi, i need to use Aspect-injector in the project .Net Framework 4.0, but
not working, because Nuget Package contains .Net Standard dependency. I
downloaded source code from github and created a new project with the code
from "AspectInjector.Broker", but in .Net Framework and this is working.
Only "AspectInjector.Broker" is referenced in project when installed nuget
package, then only this need change to .NET Framework. I believe it is
possible to have the library in NET4 and NETSTANDARD in the lib directory,
what do you think? Would it be possible?
—
Reply to this email directly, view it on GitHub
<#223>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA7HZUDMVOC7YTYR6LPPH2DX2X3E3ANCNFSM6AAAAAA43CK7O4>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Hi there, It's not possible to make the change. If we only fix the Broker for .NET 4.0, this project will build normally. However, after installing NuGet in a project, the analyzer stops working because it attempts to use the Broker, which is designed for .NET 4.0 and is not compatible with .NET Standard 2. To resolve this issue, we would need to change all projects to target .NET 4.0. However, some projects require C# 7.x, which is not compatible with .NET 4.0. Therefore, I understand that it's not possible to proceed with this change. Anyway, thank you. |
Beta Was this translation helpful? Give feedback.
-
Hi,
It should still be possible with multitarget build, right? Like packing two
DLLs, one net4, another netstandard
…On Mon, 25 Sept 2023, 01:30 Erickson Lima, ***@***.***> wrote:
Hi there,
It's not possible to make the change.
If we only fix the Broker for .NET 4.0, this project will build normally.
However, after installing NuGet in a project, the analyzer stops working
because it attempts to use the Broker, which is designed for .NET 4.0 and
is not compatible with .NET Standard 2.
To resolve this issue, we would need to change all projects to target .NET
4.0. However, some projects require C# 7.x, which is not compatible with
.NET 4.0.
Therefore, I understand that it's not possible to proceed with this change.
Anyway, thank you.
—
Reply to this email directly, view it on GitHub
<#223 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA7HZUHOC3XBVALD3S5CTJ3X4ARW5ANCNFSM6AAAAAA43CK7O4>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
I'm pretty sure there's not much code in the Broker project that requires
c#7.3, so it should be rather easy to do
…On Sun, 1 Oct 2023, 11:19 Erickson Lima, ***@***.***> wrote:
Yes, it is possible, but you must change the code to C# 4.0, compatibility
version of .NET4. Now, your code is C# 7.3.
Net4 support only C# 4.0. View this paper:
https://edsondiasalves.medium.com/which-c-version-am-i-using-a8ff51cc076d
—
Reply to this email directly, view it on GitHub
<#223 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA7HZUGIE2SIBVKULWFLQODX5CLITANCNFSM6AAAAAA43CK7O4>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Analyzers could still use netstandard version of Broker.
I'll take a look at this next week
…On Sun, 1 Oct 2023, 16:30 Erickson Lima, ***@***.***> wrote:
But are all projects, not only Broker.
Because when to run analyze, is used the Broker.dll, so analyze too need
to change Net4.
—
Reply to this email directly, view it on GitHub
<#223 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA7HZUHSDETPE62BLYRZXBLX5DPV7ANCNFSM6AAAAAA43CK7O4>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
can you try 2.8.3-pre3](https://www.nuget.org/packages/AspectInjector/2.8.3-pre3#supportedframeworks-body-tab) and tell me if it works for you? |
Beta Was this translation helpful? Give feedback.
-
I created a windows forms project with NetFramework46, but not work, because not was added in .csproj this block:
But i add manually this block and it's working. I believe it is because this target is netstandard2.0 and is not compatible with netFramework46. |
Beta Was this translation helpful? Give feedback.
-
Hi, i need to use Aspect-injector in the project .Net Framework 4.0, but not working, because Nuget Package contains .Net Standard dependency. I downloaded source code from github and created a new project with the code from "AspectInjector.Broker", but in .Net Framework and this is working. Only "AspectInjector.Broker" is referenced in project when installed nuget package, then only this need change to .NET Framework. I believe it is possible to have the library in NET4 and NETSTANDARD in the lib directory, what do you think? Would it be possible?
Beta Was this translation helpful? Give feedback.
All reactions