Are any developers using Visual Studio Code for working with GeoEvent development?

278
2
05-14-2019 05:40 AM
Highlighted
New Contributor II

We are beginning to work on developing GeoEvent services, custom connectors, etc. and we have been a Visual Studio shop. Is anyone using Visual Studio for their GeoEvent development that would be willing to share their configuration/usage tips? It looks like Visual Studio Code would support this development? Any special steps needed to take or versions to use? Is there a reason the GeoEvent SDK is not posted with the other SDKs? It seems far more difficult to obtain than the others.  @Dave Clemmer

Reply
0 Kudos
2 Replies
Highlighted
Occasional Contributor

Hi Leah Creiglow‌,

The GeoEvent SDK comes bundled with GeoEvent Server as part of the installation files. You can find the documentation and samples for it at the following locations

Windows: <ArcGIS Server installation directory>\GeoEvent\sdk (for example, C:\Program Files\ArcGIS\Server\GeoEvent\sdk).


Linux: <ArcGIS Server installation directory>/GeoEvent/sdk (for example, ~/arcgis/server/GeoEvent/sdk).

If you have seen it already, the documentation only shows examples using the Eclipse (Java EE edition) IDE. 

However, in theory, as long as you have the proper components installed on the machine per the documentation (i.e. Java SE Development Kit, Maven, etc) then you should be free to use Visual Studio for your development needs. Since each IDE will differ in terms of what it will need to write, format, and compile the code (plug-ins, packages, and the like), we cannot really give definitive responses as to which to use, because there can be several routes you can take to accomplish what you need to to build custom connectors, transports, processors, etc.

I hope this helps somewhat or can give you an idea of how to move forward. Perhaps fellow end-users who have tried Visual Studio in their development can give more specific examples. 

Reply
0 Kudos
Highlighted
Esri Contributor

I think remote debugging won't be that easy with Visual Studio Code. I might be wrong but keep it in mind.