C# Migrating VSCode Project on Mac to Visual Studio on Windows
up vote
-1
down vote
favorite
Project have been developed with Visual Studio Code on a Macbook, using C# in the .NET environment. When I am trying to run this project in Visual Studio on a computer using Windows, a lot of exceptions is caught which I have never experienced before using the Macbook. Most of them relate to objects, GDI+ and saving Graphics, also using GraphicsPath and some of them even complain about IndexOutOfBounds. These Exceptions do not get caught in Visual Studio Code, which is why I am wondering of there is any difference between developing in Visual Studio Code on MacOS and Visual Studio on Windows? References and such have been set to be the same as in VSCode.
Cannot resolve the the cause of the Exceptions, since everything is working fine on MacOS, and I have no idea why I get those.
Example: 'System.ArgumentException' in System.Drawing.dll on the following lines of code.
graphicsPath.AddArc(boundingRectangle, startAngle, sweepAngle);
graphicsPath.Transform(translateMatrix);
Since I have no issue in my original project on MacOS, I have a feeling this is not code (algorithm) related, but maybe some optimization issue related to Windows or such. Any ideas or help are appreciated!
c# .net visual-studio visual-studio-code
add a comment |
up vote
-1
down vote
favorite
Project have been developed with Visual Studio Code on a Macbook, using C# in the .NET environment. When I am trying to run this project in Visual Studio on a computer using Windows, a lot of exceptions is caught which I have never experienced before using the Macbook. Most of them relate to objects, GDI+ and saving Graphics, also using GraphicsPath and some of them even complain about IndexOutOfBounds. These Exceptions do not get caught in Visual Studio Code, which is why I am wondering of there is any difference between developing in Visual Studio Code on MacOS and Visual Studio on Windows? References and such have been set to be the same as in VSCode.
Cannot resolve the the cause of the Exceptions, since everything is working fine on MacOS, and I have no idea why I get those.
Example: 'System.ArgumentException' in System.Drawing.dll on the following lines of code.
graphicsPath.AddArc(boundingRectangle, startAngle, sweepAngle);
graphicsPath.Transform(translateMatrix);
Since I have no issue in my original project on MacOS, I have a feeling this is not code (algorithm) related, but maybe some optimization issue related to Windows or such. Any ideas or help are appreciated!
c# .net visual-studio visual-studio-code
What's the path for the dll assemblies?
– Jasen
Nov 19 at 23:16
Where do I find that?
– Oskar
Nov 19 at 23:23
It really depends on what is "the .NET environment" you are referring, as .NET Core and Mono are different things, which you failed to understand nor described which you used on macOS. Therefore, this question is incomplete and cannot be answered.
– Lex Li
Nov 20 at 5:03
I used .NET Core on macOS.
– Oskar
Nov 20 at 8:11
Additionally, the application are using about 65MB of memory when the first exception occur.
– Oskar
Nov 20 at 8:49
add a comment |
up vote
-1
down vote
favorite
up vote
-1
down vote
favorite
Project have been developed with Visual Studio Code on a Macbook, using C# in the .NET environment. When I am trying to run this project in Visual Studio on a computer using Windows, a lot of exceptions is caught which I have never experienced before using the Macbook. Most of them relate to objects, GDI+ and saving Graphics, also using GraphicsPath and some of them even complain about IndexOutOfBounds. These Exceptions do not get caught in Visual Studio Code, which is why I am wondering of there is any difference between developing in Visual Studio Code on MacOS and Visual Studio on Windows? References and such have been set to be the same as in VSCode.
Cannot resolve the the cause of the Exceptions, since everything is working fine on MacOS, and I have no idea why I get those.
Example: 'System.ArgumentException' in System.Drawing.dll on the following lines of code.
graphicsPath.AddArc(boundingRectangle, startAngle, sweepAngle);
graphicsPath.Transform(translateMatrix);
Since I have no issue in my original project on MacOS, I have a feeling this is not code (algorithm) related, but maybe some optimization issue related to Windows or such. Any ideas or help are appreciated!
c# .net visual-studio visual-studio-code
Project have been developed with Visual Studio Code on a Macbook, using C# in the .NET environment. When I am trying to run this project in Visual Studio on a computer using Windows, a lot of exceptions is caught which I have never experienced before using the Macbook. Most of them relate to objects, GDI+ and saving Graphics, also using GraphicsPath and some of them even complain about IndexOutOfBounds. These Exceptions do not get caught in Visual Studio Code, which is why I am wondering of there is any difference between developing in Visual Studio Code on MacOS and Visual Studio on Windows? References and such have been set to be the same as in VSCode.
Cannot resolve the the cause of the Exceptions, since everything is working fine on MacOS, and I have no idea why I get those.
Example: 'System.ArgumentException' in System.Drawing.dll on the following lines of code.
graphicsPath.AddArc(boundingRectangle, startAngle, sweepAngle);
graphicsPath.Transform(translateMatrix);
Since I have no issue in my original project on MacOS, I have a feeling this is not code (algorithm) related, but maybe some optimization issue related to Windows or such. Any ideas or help are appreciated!
c# .net visual-studio visual-studio-code
c# .net visual-studio visual-studio-code
asked Nov 19 at 22:10
Oskar
34
34
What's the path for the dll assemblies?
– Jasen
Nov 19 at 23:16
Where do I find that?
– Oskar
Nov 19 at 23:23
It really depends on what is "the .NET environment" you are referring, as .NET Core and Mono are different things, which you failed to understand nor described which you used on macOS. Therefore, this question is incomplete and cannot be answered.
– Lex Li
Nov 20 at 5:03
I used .NET Core on macOS.
– Oskar
Nov 20 at 8:11
Additionally, the application are using about 65MB of memory when the first exception occur.
– Oskar
Nov 20 at 8:49
add a comment |
What's the path for the dll assemblies?
– Jasen
Nov 19 at 23:16
Where do I find that?
– Oskar
Nov 19 at 23:23
It really depends on what is "the .NET environment" you are referring, as .NET Core and Mono are different things, which you failed to understand nor described which you used on macOS. Therefore, this question is incomplete and cannot be answered.
– Lex Li
Nov 20 at 5:03
I used .NET Core on macOS.
– Oskar
Nov 20 at 8:11
Additionally, the application are using about 65MB of memory when the first exception occur.
– Oskar
Nov 20 at 8:49
What's the path for the dll assemblies?
– Jasen
Nov 19 at 23:16
What's the path for the dll assemblies?
– Jasen
Nov 19 at 23:16
Where do I find that?
– Oskar
Nov 19 at 23:23
Where do I find that?
– Oskar
Nov 19 at 23:23
It really depends on what is "the .NET environment" you are referring, as .NET Core and Mono are different things, which you failed to understand nor described which you used on macOS. Therefore, this question is incomplete and cannot be answered.
– Lex Li
Nov 20 at 5:03
It really depends on what is "the .NET environment" you are referring, as .NET Core and Mono are different things, which you failed to understand nor described which you used on macOS. Therefore, this question is incomplete and cannot be answered.
– Lex Li
Nov 20 at 5:03
I used .NET Core on macOS.
– Oskar
Nov 20 at 8:11
I used .NET Core on macOS.
– Oskar
Nov 20 at 8:11
Additionally, the application are using about 65MB of memory when the first exception occur.
– Oskar
Nov 20 at 8:49
Additionally, the application are using about 65MB of memory when the first exception occur.
– Oskar
Nov 20 at 8:49
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53383365%2fc-sharp-migrating-vscode-project-on-mac-to-visual-studio-on-windows%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
What's the path for the dll assemblies?
– Jasen
Nov 19 at 23:16
Where do I find that?
– Oskar
Nov 19 at 23:23
It really depends on what is "the .NET environment" you are referring, as .NET Core and Mono are different things, which you failed to understand nor described which you used on macOS. Therefore, this question is incomplete and cannot be answered.
– Lex Li
Nov 20 at 5:03
I used .NET Core on macOS.
– Oskar
Nov 20 at 8:11
Additionally, the application are using about 65MB of memory when the first exception occur.
– Oskar
Nov 20 at 8:49