No need for “external” PIAs (primary interop assembly) like with Arcobjects. Simply install ArcGIS Pro.
This is the fully fledged 64-bit version that will use more than 4GB of RAM for processing a long drawback of ESRI - welcome to the 21st century
Still limited
At Final Release: No APIs for: Facility Network Network Analysis
Labelling Data Reviewer APIs still undecided for: Data Management 3D
Analysis (TIN, LAS) Layout ArcGIS Pro .NET SDK
ArcGIS Pro API Workflows at 1.0, 1.1: 2D and 3D editing 2D and 3D Map
interactions (author, query, time, visualize) Content management and
sharing (online, portals, web maps) Fine grained APIs for Geometry and
Geodatabase Leverage .Net language features and async patterns
What is not supported in the API for Pro?:
Custom data source and feature class extensions Custom extensions
(edit, feature class, map) Custom Raster functions Custom GP functions
Standalone “ArcEngine” applications ArcGIS Pro .NET SDK: The Road
Ahead
If you require any of the .NET 4.0 Framework functionality, you can
extend Esri products with components written in the .NET 4.0
Framework. However, it's your responsibility to redistribute and/or
verify that the .NET 4.0 Framework exists on the target system.
I think the beta doc might be a little out of date. I was told to look at the factory methods. (MapFactory.Create, ItemFactory.Create, etc which will be the way to go when the SDK is released at 1.1)
Try this: (note, the map is created in the projectpane, but is not automatically opened)
Best Answer
It is a replacement
ArcGIS Pro .NET SDK: The Road Ahead – SDK and API
No need for “external” PIAs (primary interop assembly) like with Arcobjects. Simply install ArcGIS Pro.
This is the fully fledged 64-bit version that will use more than 4GB of RAM for processing a long drawback of ESRI - welcome to the 21st century
Still limited
source: http://proceedings.esri.com/library/userconf/proc14/tech-workshops/tw_725.pdf