I've just coped a release version of my application onto a fresh non-development machine and I've found whenever a Scichart surface loads the program crashes with the standard "Application has stopped working: A problem caused the program to stop working correctly."
I've got two identical machines that I've loaded the application onto, however, I was using one while using the trial version of Scichart, so I'd installed the trial onto it so I was able to run the software for a demo. Now I've got a full license, it's all fine on that machine. But I can confidently rule out hardware.
I think I might not be deploying the license correctly? But if that were the case the charts should be blank rather than crash the program.
I've updated to the latest 4.05 release.
Any ideas where to look for the problem? Cheers.
It sounds to me like either the application itself is throwing an Exception, or the .NET4.0 Runtime is not installed on the target PC.
To check the latter, ensure that .NET4.0 Runtime (or 4.5/4.6 if you are compiling for this version) is installed on the target PC.
If that doesn't help, you need to write a global catch-all handler in your WPF application and log the exception that you are getting. Then, from the exception message, stack trace, inner exception (if any) you should be able to identify the problem.
Also, the WPF Charts with DirectX Hardware Acceleration have some dependencies, but SciChart is designed to fall back to software rendering if dependencies are not found.
Finally, certain components in SciChart, such as WPF 3D Charts, require the Visual C++ 2013 Runtime. There should be an exception thrown if VC++2013 is not found on the target PC. But apart from that, the dependencies are pretty slim.
Comment here with what you find.
Related
Its saying "The project needs to be deployed before it can be started.
Verify the project is selected to be deployed or deploy it explicitly by clicking one of the deployment commands in the Build Menu."
I have tried to explicitly deploy it from the build menu but its all in vain. Not able to understand whats wrong.
It may be caused by the fact that no devices are detected.If you try to debug on a real device, it may no be detected by your computer or VS. If you use the emulator, it may be an error with the emulator (like for example, the emulator doesn't launch, so you can't deploy on nothing).
Try removing Apache Cordova Tools Package.
Worked for me.
I have a Windows Phone 8.1 project that refers to a Windows Runtime Component, which exposes some other native projects of mine. The problem is I get a System.IO.FileNotFoundException when running it on emulator. However, if I catch the exception and check exception.FileName, it's null.
The guy here has mentioned he used ProcMon to figure out which file was missing. How do I use ProcMon to monitor file accesses made by an emulator? I tried monitoring the emulator process itself, but that didn't produce any info.
There is no way provided to run desktop apps such as ProcMon on the emulator. The linked post was able to run ProcMon on Windows, not on Windows Phone.
Your best bet is to debug the app running on the emulator. Use the unmanaged debugger so it can break in the native code, break on the first chance exception, then see where in the stack this is called from. Once you know where the problem is, you can set a break point at the beginning of the function then either step through or set a trace point to see what files are being used and what the app thinks it is doing then.
I'm trying to create the store packages for a windows store app that includes a Windows Run Time component for running a background process that updates the Lock Screen. The app runs fine, but when I try to create the store packages I get this error:
There was a mismatch between the processor architecture of the project being built "AMD64" and the processor architecture of the reference "WindowsRuntimeComponent1, Version=1.0.0.0, Culture=neutral, processorArchitecture=x86", "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
There seems like there's a dozen of different combinations I can tweak in the configuration manager, and there's very little help online regarding this problem. This is very frustrating - the app runs fine on my own machine, and now when I'm ready to finalize and upload the app I hit this brick wall.
Go to the project properties in visual studio. Under Compile, change Target CPU to x86
You get to the project properties by:
go the solution explorer
right click the phone app project
click properties in the context menu
On the left hand side, there should be a vertical nav menu, click Compile
Change the Target CPU to x86 and save
Nvidia has released extended eclipse for CUDA 5. They have Nsight plugin for VS2010 also. In VS2010 we can stop program execution at breakpoint in kernel but how to achieve this functionality in eclipse on Linux? I don't see any nsight specific keys to stop execution. I tried changing perspective but it debugs as a normal C/C++ application. I'm using Tesla C2070, Intel Xeon 8 core machine with Linux.
I'm from Nsight Eclipse Edition team.
Our goal is specifically for the application to be debugged as a normal C/C++ application. This means that you can set breakpoints, use "run to line", etc. regardless of whether you debug host or device code.
Basically, the process is quite standard for Eclipse:
Create a project (you can also import existing executable)
Click debug button
Debugger will run and by default will break in the main function. Note that no device code posted on the device so you will only see the host thread.
Set a breakpoint in the device code and hit resume (note that Breakpoints view toolbar also allows you setting breakpoint on any CUDA kernel launch)
Debugger will break when device code reaches the breakpoint. You can inspect your application state using visual debugger UI.
Couple things, and not sure which solved the issue. Drivers updated to latest ones with RC5.0, but I chose to run VNC server instead of native X server. Then the CUDA card(s) are dedicated to my apps and debugging, and it works like a charm, and now accessible from everywhere.
Eugene,
I just installed Cuda 5, and I wasn't able to break in any kernel code. It was a clean install of centos 5.5, with a fresh download of cuda-5, and i am running on a asus g71x laptop which has a gtx260m installed.
I thought maybe you cant run display and dedbug on one device still, so i switched to non-nv x display, but still had same issue, cant stop in the kernel code.
Have you tried CUDA 5.0 RC1? It is available now. You can download and try it. And I have tried the Nsight in it, it works well for debugging.
Best regards!
The 304.43 NVIDIA Driver does not let users other than root debug their CUDA application.
That problem is not present in any past or future public releases. The CUDA documentation recommends using only drivers listed in the CUDA DevZone. The 304.43 driver is not one of them.
That may or may not be the issue you are hitting. But I thought it was worth mentioning.
I would like to ask help for a problem that I am facing. I was running a long task within a website. Because it was taking some time to process the task, I decided to change the structure. Shortly, now I am calling an exe from the website and monitoring the process. All is fine on my development environment. But when I try to run the exe on my prod environment, I get the following exception message. I use System.Data.OracleClient to connect to Oracle database.
The type initializer for 'System.Data.OracleClient.OracleConnection' threw an exception.
This happens when I call the exe from the website. I created a winforms app to test the exe. And if I call the exe from my winforms app (in the same way that I call from the website) everything works fine.
I searched the exception online. There were 2 suggestions I found.
1-) Different version of Oracle Client : This is why I created the test winforms app. It ran all fine. So I don't think Oracle client is the issue unless I'm missing something.
2-) 32-bit/64-bit OS issue : I initially compiled the exe targeting 32 bit environment. And my prod environment is 64 bit. So I tried to compile targetting 64 bit but got the same exception. Plus, 32-bit exe runs without any problems with my winforms test application. Also my development environment is 64bit as well, but I don't get the exception there.
Any ideas will be appreciated...
EDIT : I couldn't find a solution to type initializer exception. Actually I didn't have time to dig into it. So what I did instead is to call a winforms exe and simulating it's button click to call the actual exe. I didn't like the solution but I had to move on. I am no more getting the OracleConnection exception.