Setting Embed Interop Types in ArcObjects to True or False?
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
2
down vote
favorite
I took over a new project with some legacy ArcObjects code and the original developer set the ArcObjects references "Embed Interop Types" property in Visual Studio to a mixture of "True" and "False".
From my experience, the differences mostly seem to be some syntax changes with things such as creating new objects.
Is there a reason to choose "True" rather than "False"?
arcobjects c# visual-studio
add a comment |Â
up vote
2
down vote
favorite
I took over a new project with some legacy ArcObjects code and the original developer set the ArcObjects references "Embed Interop Types" property in Visual Studio to a mixture of "True" and "False".
From my experience, the differences mostly seem to be some syntax changes with things such as creating new objects.
Is there a reason to choose "True" rather than "False"?
arcobjects c# visual-studio
add a comment |Â
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I took over a new project with some legacy ArcObjects code and the original developer set the ArcObjects references "Embed Interop Types" property in Visual Studio to a mixture of "True" and "False".
From my experience, the differences mostly seem to be some syntax changes with things such as creating new objects.
Is there a reason to choose "True" rather than "False"?
arcobjects c# visual-studio
I took over a new project with some legacy ArcObjects code and the original developer set the ArcObjects references "Embed Interop Types" property in Visual Studio to a mixture of "True" and "False".
From my experience, the differences mostly seem to be some syntax changes with things such as creating new objects.
Is there a reason to choose "True" rather than "False"?
arcobjects c# visual-studio
arcobjects c# visual-studio
edited 4 mins ago
PolyGeoâ¦
51.9k1778233
51.9k1778233
asked 4 hours ago
arcobjection
265
265
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
4
down vote
The important difference is the way interop information is stored; either in your assembly, or in an external PIA. Because ArcGIS already provides PIA's, you should always set 'Embed Interop Types' to false for ArcGIS solutions.
The following paragraphs are taken from http://resources.arcgis.com/en/help/arcobjects-net/conceptualhelp/index.html#//000100000nzv000000
Using the Embed Interop Types property on referenced assemblies
Embed Interop Types is a new feature of the .NET 4.0 Framework that allows you to include the attribute information that is normally stored in the Primary Interop Assembly (PIA) in the executable or dynamic-link library (DLL) instead. This was introduced because deployment of managed solutions built on certain COM-based technologies was difficult because the deployment and verification of the PIA was also done on the target machine.
By default, when you add a PIA to a Visual Studio 2010 .NET 4.0 project without using the Add ArcGIS Reference plug-in, the PIA's Embed Interop Types property is set to true. The best practice is to change this setting to false when deploying customizations for ArcGIS, because the ArcGIS installer lays down the appropriate PIAs and assemblies on the system; you should not include any with your solution.
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
4
down vote
The important difference is the way interop information is stored; either in your assembly, or in an external PIA. Because ArcGIS already provides PIA's, you should always set 'Embed Interop Types' to false for ArcGIS solutions.
The following paragraphs are taken from http://resources.arcgis.com/en/help/arcobjects-net/conceptualhelp/index.html#//000100000nzv000000
Using the Embed Interop Types property on referenced assemblies
Embed Interop Types is a new feature of the .NET 4.0 Framework that allows you to include the attribute information that is normally stored in the Primary Interop Assembly (PIA) in the executable or dynamic-link library (DLL) instead. This was introduced because deployment of managed solutions built on certain COM-based technologies was difficult because the deployment and verification of the PIA was also done on the target machine.
By default, when you add a PIA to a Visual Studio 2010 .NET 4.0 project without using the Add ArcGIS Reference plug-in, the PIA's Embed Interop Types property is set to true. The best practice is to change this setting to false when deploying customizations for ArcGIS, because the ArcGIS installer lays down the appropriate PIAs and assemblies on the system; you should not include any with your solution.
add a comment |Â
up vote
4
down vote
The important difference is the way interop information is stored; either in your assembly, or in an external PIA. Because ArcGIS already provides PIA's, you should always set 'Embed Interop Types' to false for ArcGIS solutions.
The following paragraphs are taken from http://resources.arcgis.com/en/help/arcobjects-net/conceptualhelp/index.html#//000100000nzv000000
Using the Embed Interop Types property on referenced assemblies
Embed Interop Types is a new feature of the .NET 4.0 Framework that allows you to include the attribute information that is normally stored in the Primary Interop Assembly (PIA) in the executable or dynamic-link library (DLL) instead. This was introduced because deployment of managed solutions built on certain COM-based technologies was difficult because the deployment and verification of the PIA was also done on the target machine.
By default, when you add a PIA to a Visual Studio 2010 .NET 4.0 project without using the Add ArcGIS Reference plug-in, the PIA's Embed Interop Types property is set to true. The best practice is to change this setting to false when deploying customizations for ArcGIS, because the ArcGIS installer lays down the appropriate PIAs and assemblies on the system; you should not include any with your solution.
add a comment |Â
up vote
4
down vote
up vote
4
down vote
The important difference is the way interop information is stored; either in your assembly, or in an external PIA. Because ArcGIS already provides PIA's, you should always set 'Embed Interop Types' to false for ArcGIS solutions.
The following paragraphs are taken from http://resources.arcgis.com/en/help/arcobjects-net/conceptualhelp/index.html#//000100000nzv000000
Using the Embed Interop Types property on referenced assemblies
Embed Interop Types is a new feature of the .NET 4.0 Framework that allows you to include the attribute information that is normally stored in the Primary Interop Assembly (PIA) in the executable or dynamic-link library (DLL) instead. This was introduced because deployment of managed solutions built on certain COM-based technologies was difficult because the deployment and verification of the PIA was also done on the target machine.
By default, when you add a PIA to a Visual Studio 2010 .NET 4.0 project without using the Add ArcGIS Reference plug-in, the PIA's Embed Interop Types property is set to true. The best practice is to change this setting to false when deploying customizations for ArcGIS, because the ArcGIS installer lays down the appropriate PIAs and assemblies on the system; you should not include any with your solution.
The important difference is the way interop information is stored; either in your assembly, or in an external PIA. Because ArcGIS already provides PIA's, you should always set 'Embed Interop Types' to false for ArcGIS solutions.
The following paragraphs are taken from http://resources.arcgis.com/en/help/arcobjects-net/conceptualhelp/index.html#//000100000nzv000000
Using the Embed Interop Types property on referenced assemblies
Embed Interop Types is a new feature of the .NET 4.0 Framework that allows you to include the attribute information that is normally stored in the Primary Interop Assembly (PIA) in the executable or dynamic-link library (DLL) instead. This was introduced because deployment of managed solutions built on certain COM-based technologies was difficult because the deployment and verification of the PIA was also done on the target machine.
By default, when you add a PIA to a Visual Studio 2010 .NET 4.0 project without using the Add ArcGIS Reference plug-in, the PIA's Embed Interop Types property is set to true. The best practice is to change this setting to false when deploying customizations for ArcGIS, because the ArcGIS installer lays down the appropriate PIAs and assemblies on the system; you should not include any with your solution.
answered 4 hours ago
Berend
2,410518
2,410518
add a comment |Â
add a comment |Â
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
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fgis.stackexchange.com%2fquestions%2f298043%2fsetting-embed-interop-types-in-arcobjects-to-true-or-false%23new-answer', 'question_page');
);
Post as a guest
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
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
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