+ Reply to Thread
Results 1 to 7 of 7

Thread: WPF API - non runtime (3.0 vs 2.4)

  1. #1
    Angel Gonzalez
    Join Date
    Apr 2010
    Posts
    150
    Points
    0
    Answers Provided
    0


    0

    Default WPF API - non runtime (3.0 vs 2.4)

    The 2.4 version of the WPF API I was able to publish an application using clickonce and have users on my network use the app. Can I still do the same thing at 3.0 without have to use any licenses? All references to any maps will point directly to ArcServer.

    Thanks

  2. #2
    Mike Branscomb

    Join Date
    Feb 2010
    Posts
    882
    Points
    359
    Answers Provided
    59


    1

    Default Re: WPF API - non runtime (3.0 vs 2.4)

    Hi,

    If you are only using services from ArcGIS Server or ArcGIS Online that represents a "Basic" license in the new ArcGIS Runtime SDK for WPF (v3.0 of the API). You will need to set the license string, but at the Basic level the license continues to be free.


    Cheers

    Mike
    ArcGIS Runtime Product Engineer

  3. #3
    Angel Gonzalez
    Join Date
    Apr 2010
    Posts
    150
    Points
    0
    Answers Provided
    0


    0

    Default Re: WPF API - non runtime (3.0 vs 2.4)

    Thanks for the info.

    One more question, can I install 2.4 and 3.0 Pre-release on the same machine and use 10.0?

    Also if I only use ArcGIS Server layers/features in my 3.0 WPF application do I still need to use the deployment tool to deploy the app or can I still use Clickonce to deploy the app to our users in our organization (behind a firewall) as I currently do now.

    Thanks.

  4. #4
    Mike Branscomb

    Join Date
    Feb 2010
    Posts
    882
    Points
    359
    Answers Provided
    59


    0

    Default Re: WPF API - non runtime (3.0 vs 2.4)

    Quote Originally Posted by angelg View Post
    Thanks for the info.

    One more question, can I install 2.4 and 3.0 Pre-release on the same machine and use 10.0?

    Also if I only use ArcGIS Server layers/features in my 3.0 WPF application do I still need to use the deployment tool to deploy the app or can I still use Clickonce to deploy the app to our users in our organization (behind a firewall) as I currently do now.

    Thanks.
    Hi,

    Yes, you can install 2.4 and 3.0 Pre-release on the same machine but the default assembly references and toolbox UI components will be updated to v3.0.

    If you only use ArcGIS Server layers you will still need to use the Deployment Builder but this does not actually deploy the app, it just helps you to create an ArcGIS Runtime deployment folder with the minimum components you need. If you're only using services then the ArcGIS Runtime deployment will be very small. You will still need to deploy the ESRI.ArcGIS.Client.dll assembly with your application (plus any other WPF client assemblies you use). ClickOnce deployment should work fine - please let me know as soon as possible if you experience any problems and we'll investigate.

    Cheers

    Mike
    ArcGIS Runtime Product Engineer

  5. #5
    Brian Locke
    Join Date
    Jul 2010
    Posts
    82
    Points
    0
    Answers Provided
    1


    0

    Default Re: WPF API - non runtime (3.0 vs 2.4)

    Dragging and dropping Runtime Application works great, have it working against ArcGIS Server and can do a quite a few different tasks yet when I deploy via ClickOnce -- deploys and have alot of people using this application works great until I try to start a GeometryService-- getting this and have gotten of reports on about 10 machines so far


    Log Name: Application
    Source: Application Error
    Date: 05/29/2013 10:01:10 PM
    Event ID: 1000
    Task Category: (100)
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: cfpa03gis.ODF.STATE.OR.US
    Description:
    Faulting application name: WRMS.exe, version: 1.0.0.0, time stamp: 0x51a6dcbc
    Faulting module name: KERNELBASE.dll, version: 6.1.7601.18015, time stamp: 0x50b8479b
    Exception code: 0xe0434352
    Fault offset: 0x0000000000009e5d
    Faulting process id: 0x6ea8
    Faulting application start time: 0x01ce5cf2ad0160d3
    Faulting application path: C:\Users\blocke\AppData\Local\Apps\2.0\WO9WVNVW.X30\K1H5434P.O2E\wrms..tion_a062cf3d3dbaacfb_0001.0000_2b6e0cc01b655b6e\WRMS.exe
    Faulting module path: C:\Windows\system32\KERNELBASE.dll
    Report Id: f1082f3c-c8e5-11e2-98a6-d067e544e921
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-05-30T05:01:10.000000000Z" />
    <EventRecordID>26839</EventRecordID>
    <Channel>Application</Channel>
    <Computer>cfpa03gis.ODF.STATE.OR.US</Computer>
    <Security />
    </System>
    <EventData>
    <Data>WRMS.exe</Data>
    <Data>1.0.0.0</Data>
    <Data>51a6dcbc</Data>
    <Data>KERNELBASE.dll</Data>
    <Data>6.1.7601.18015</Data>
    <Data>50b8479b</Data>
    <Data>e0434352</Data>
    <Data>0000000000009e5d</Data>
    <Data>6ea8</Data>
    <Data>01ce5cf2ad0160d3</Data>
    <Data>C:\Users\blocke\AppData\Local\Apps\2.0\WO9WVNVW.X30\K1H5434P.O2E\wrms..tion_a062cf3d3dbaacfb_0001.0000_2b6e0cc01b655b6e\WRMS.exe</Data>
    <Data>C:\Windows\system32\KERNELBASE.dll</Data>
    <Data>f1082f3c-c8e5-11e2-98a6-d067e544e921</Data>
    </EventData>
    </Event>

  6. #6
    Brian Locke
    Join Date
    Jul 2010
    Posts
    82
    Points
    0
    Answers Provided
    1


    0

    Default Re: WPF API - non runtime (3.0 vs 2.4)

    Accompanied error with it

    Log Name: Application
    Source: .NET Runtime
    Date: 05/29/2013 10:01:09 PM
    Event ID: 1026
    Task Category: None
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: cfpa03gis.ODF.STATE.OR.US
    Description:
    Application: WRMS.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.InvalidOperationException
    Stack:
    at ESRI.ArcGIS.Client.Tasks.GeometryService.LengthsAsync(System.Collections.Generic.IList`1<ESRI.ArcGIS.Client.Graphic>, System.Nullable`1<ESRI.ArcGIS.Client.Tasks.LinearUnit>, ESRI.ArcGIS.Client.Tasks.CalculationType, System.Object)
    at WRMS.Framework.ViewModels.MeasureVM.<measure>b__4(ESRI.ArcGIS.Client.Local.LocalGeometryService)
    at ESRI.ArcGIS.Client.Local.LocalService.FailStart(System.Exception)
    at ESRI.ArcGIS.Client.Local.Internal.Requests.ProcessResponse[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](System.String, System.String, System.Exception, Boolean, System.String, System.Action`2<System.__Canon,ESRI.ArcGIS.Client.Local.Internal.RequestInfo>)
    at ESRI.ArcGIS.Client.Local.Internal.Requests+<>c__DisplayClass7`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].<Start>b__2(System.Object, System.Net.UploadStringCompletedEventArgs)
    at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
    at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
    at System.Windows.Threading.Dispatcher.WrappedInvoke(System.Delegate, System.Object, Int32, System.Delegate)
    at System.Windows.Threading.DispatcherOperation.InvokeImpl()
    at System.Threading.ExecutionContext.runTryCode(System.Object)
    at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode, CleanupCode, System.Object)
    at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
    at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
    at System.Windows.Threading.DispatcherOperation.Invoke()
    at System.Windows.Threading.Dispatcher.ProcessQueue()
    at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
    at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
    at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
    at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
    at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
    at System.Windows.Threading.Dispatcher.WrappedInvoke(System.Delegate, System.Object, Int32, System.Delegate)
    at System.Windows.Threading.Dispatcher.InvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
    at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
    at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
    at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
    at System.Windows.Application.RunInternal(System.Windows.Window)
    at System.Windows.Application.Run()
    at WRMS.App.Main()

    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name=".NET Runtime" />
    <EventID Qualifiers="0">1026</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-05-30T05:01:09.000000000Z" />
    <EventRecordID>26838</EventRecordID>
    <Channel>Application</Channel>
    <Computer>cfpa03gis.ODF.STATE.OR.US</Computer>
    <Security />
    </System>
    <EventData>
    <Data>Application: WRMS.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.InvalidOperationException
    Stack:
    at ESRI.ArcGIS.Client.Tasks.GeometryService.LengthsAsync(System.Collections.Generic.IList`1&lt;ESRI.ArcGIS.Client.Graphic&gt;, System.Nullable`1&lt;ESRI.ArcGIS.Client.Tasks.LinearUnit&gt;, ESRI.ArcGIS.Client.Tasks.CalculationType, System.Object)
    at WRMS.Framework.ViewModels.MeasureVM.&lt;measure&gt;b__4(ESRI.ArcGIS.Client.Local.LocalGeometryService)
    at ESRI.ArcGIS.Client.Local.LocalService.FailStart(System.Exception)
    at ESRI.ArcGIS.Client.Local.Internal.Requests.ProcessResponse[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](System.String, System.String, System.Exception, Boolean, System.String, System.Action`2&lt;System.__Canon,ESRI.ArcGIS.Client.Local.Internal.RequestInfo&gt
    at ESRI.ArcGIS.Client.Local.Internal.Requests+&lt;&gt;c__DisplayClass7`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].&lt;Start&gt;b__2(System.Object, System.Net.UploadStringCompletedEventArgs)
    at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
    at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
    at System.Windows.Threading.Dispatcher.WrappedInvoke(System.Delegate, System.Object, Int32, System.Delegate)
    at System.Windows.Threading.DispatcherOperation.InvokeImpl()
    at System.Threading.ExecutionContext.runTryCode(System.Object)
    at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode, CleanupCode, System.Object)
    at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
    at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
    at System.Windows.Threading.DispatcherOperation.Invoke()
    at System.Windows.Threading.Dispatcher.ProcessQueue()
    at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
    at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
    at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
    at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
    at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
    at System.Windows.Threading.Dispatcher.WrappedInvoke(System.Delegate, System.Object, Int32, System.Delegate)
    at System.Windows.Threading.Dispatcher.InvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
    at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
    at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
    at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
    at System.Windows.Application.RunInternal(System.Windows.Window)
    at System.Windows.Application.Run()
    at WRMS.App.Main()
    </Data>
    </EventData>
    </Event>

  7. #7
    Brian Locke
    Join Date
    Jul 2010
    Posts
    82
    Points
    0
    Answers Provided
    1


    0

    Unhappy Re: WPF API - non runtime (3.0 vs 2.4)

    Is this something to do with the manifest and clickonce/Certificate ??? I am totally lost on this and have been trying to figure this out for quite some time?????

+ Reply to Thread

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts