This is fun! I did this same thing for my previous job: Wrapped the ArcGIS JS API with JS interop and turned the parts and pieces into Blazor components. There were definitely a lot of quirks (hydrating objects in JS without all of the properties being populated when sending them to .NET or from .NET to the JS function). I'm looking forward to providing this info to the new developer (if they have one, yet).
Open to using Geoblazor to avoid using Node. However, there are thousands of things that can be done with the ArcGIS Javascript Library without presenting a developer key. I do not want my key in a place where it can be compromised by a hacker. However in order to even get started with GeoBlazor you supposedly need a developer key. How is this right? My taxes went to develop ArcGIS.
Great job! We are starting on a system using GeoBlazor!
This is fun! I did this same thing for my previous job: Wrapped the ArcGIS JS API with JS interop and turned the parts and pieces into Blazor components. There were definitely a lot of quirks (hydrating objects in JS without all of the properties being populated when sending them to .NET or from .NET to the JS function). I'm looking forward to providing this info to the new developer (if they have one, yet).
Open to using Geoblazor to avoid using Node. However, there are thousands of things that can be done with the ArcGIS Javascript Library without presenting a developer key. I do not want my key in a place where it can be compromised by a hacker. However in order to even get started with GeoBlazor you supposedly need a developer key. How is this right? My taxes went to develop ArcGIS.
Amazing
Hi everyone