I created a 32 bit program with Rad studio 10.4 in C++. This program must communicate with 2 APIs.
My development machine is running Windows 10 x64 and all tests are going well. The program communicates perfectly with APIs.
I put the program in production at my client, on a Windows 7 x64 machine and there, the communication is not done, return code 0.
I test on a new VM in Windows 7 x64 and the problem is the same.
I'm testing on a new VM in Windows 10 x64 and no worries, communication is fine.
I of course disabled the firewall, also added rules in the firewall but nothing changes.
Do you have any idea where the problem could come from ?
Thanks a lot
this->RESTClient_maj->BaseURL = "urlapi";
this->RESTRequest_maj->Params->Items[0]->Value = "token 1234";
this->RESTRequest_maj->Execute();
I use components from Rad Studio and get and patch methods.
what additional information can I provide ?
Related
I'm working on an AIR app that uses a Native Extension for windows that I developed for the same project. The app calls an ANE method called pingFunction and passes it a String containing the IP address where the pingFunction will perform, believe it or not, a ping test.
The application and it's ANE work great on Flash Builder and even after making it a release, they keep working like a charm on the development PC. The problem is that I've tried on two other computers and the application is throwing the following error:
ArgumentError: Error #3500: The extension context does not have a method with the name pingFunction.
at flash.external::ExtensionContext/_call()
at flash.external::ExtensionContext/call()
at com.mycompanyname.myappname::MyAppName/sendPing()[...
At the beggining I thought I had to do with the fact that I was using a DLL I compiled using the Debug configuration on Visual Studio instead of the Release configuration, because I read that sometimes the a debug-version of a DLL can use external DLLs. So, I changed it and rebuilt the whole library as a release build. Sadly for me, I'm still experiencing the same result.
Also, I tried changing the swf-version of both the AIR app and the ANE to the AIR SDK version I'm using (14.0), and got again the same error.
The development computer is running Windows 8.1 and the others, where the app is not working, Windows 7 and Windows 7 Service Pack 1.
Any ideas about why this is happening? Any questions or comments that might lead me to the right track will be deeply appreciated.
Error#3500 is coming because you don't have the required runtime installed on those machines, which is necessary to execute any c++ code .
On your development machine you have visual studio installed and hence you also have msvcr.
Solution of the problem is:
Install msvcr i.e. Microsoft Visual c++ redistribution - 2012 from here.
you need msvcr anywhere you want to run any VS compiled c++ code.
I am using Microsoft Visual Studio 2008 for development for Motorola WR41N0, which has Windows CE 7.0 operating system. As program was initially used on Windows CE 5.0, I just changed settings to fit to new operating system. Everything is going ok, except debugging. I am able to set breakpoint and it stops on it, but I am unable to make steps (F10 key). I made a build for older device Motorola WT4090 with Windows CE 5.0 and it was running ok and I was also able to debug in steps. Then I switched devices and it deployed older version on new device. Its graphical interface didn't start, but I was able to debug start routine in steps. After rebuild and redeploy I wasn't able to debug in steps again. Please give me some advice what to do, thank you.
If you are developing using C/C++ you may need to install those patches on your VS machine:
http://www.microsoft.com/en-us/download/details.aspx?id=11935
http://support.microsoft.com/kb/2483802
(should be the same fix, but it's not easy to understand this on MSDN...)
I'm working on Visual Studio 2012 running on Windows 8 (32 bit), developing Windows Store app with C++
The app runs smooth on "local machine". But when I try to run it on the simulator, Build and Deploy succeeds but the simulator keeps loading forever! (dots coming from left and leaving at right)
When I close the simulator from the taskbar, VS gives me the following error: Unable to start the simulator. Cannot process request because the process (####) has exited.
I've been searching everywhere for a solution for a week now. The possible solutions I found were:
1. Changing the fDenyChildConnections registry.
2. Checking the "Automatically use my Windows logon name and password (and domain if any)" checkbox from the security tab of the network.
3. Updating graphics driver.
4. Disconnecting all networks.
5. Restarting VS/making new project.
6. Launching simulator from C:\Program Files\Common Files\microsoft shared\Windows Simulator\11.0\Microsoft.Windows.Simulator.exe
7. Updating VS.
The problem is still there. Does anybody have a solution?
I performed a clean install of Windows 8.1 x64 and the simulator is running smoothly. I guess running 32 bit windows on a 64 bit architecture was the cause of this issue.
Try to see if "Remote Desktop Services" is enabled, if no enable it as manual and start it.
I had the same issue and the reason was lack of Hyper-V. I installed Hyper-V and the simulator worked.
Disclaimer: I'm quite new to the MSFT tech world and only started Windows Phone development a month or so ago.
I am unable to figure out how to log information to the Visual Studio Output window from within a C# and C++ (Direct3D) Windows Phone 8 App. Is this possible?
I am building in debug mode, targeting Windows Phone 8, running in the XDE emulator and my development machine is a Windows 8 box with VS2012 Ultimate installed. My App runs fine, my Direct3D scene renders normally, but I can't log anything! This makes tracing code execution difficult and forces me to use breakpoints (which can be overkill in many situations).
I've been searching far and wide and have tried many methods (OutputDebugString being one of them). I can't see anything on MSDN about this - why is this not documented anywhere?
Yep, it's possible to write debug strings from WP8 C++ to the output window in VS2012. I actually have an example of that here.
1) Invoke OutputDebugString from C++.
void Direct3DInterop::MyButtonWasClicked()
{
OutputDebugString(L"Button was clicked!");
}
2) Before running the app make sure to change to the native debugger from the managed debugger in the project's properties.
I believe the methods in System.Diagnostics.Debug (specifically the overloads of WriteLine()) work...although I haven't tried them with C++ apps.
This question already has answers here:
Closed 10 years ago.
Possible Duplicate:
Why simple console app runs but dialog based does not run in WIN CE 6.0?
My device is iPA280. It has:
Main Processor: Marvell PXA-300 (XScale ARM) # 624 MHz
Operating System: WinCE 6 pro
I am developing an application in embedded Visual C++ 4 with service pack 4 for this device. Which configuration (ARMV4, ARMV4I, MIPSII and...) should I use for building correct .EXE file for this device?
I have tested most of configurations but my application only works in emulator correctly and .exe files in other configurations do not work on device. some of .exe files has invalid EXE message and some do not run without any message or error or warning.
Thanks,
ARM v5 is backwards compatible with the ARMv4 instruction set, so I don't think the problem lies here. The program may fail to start on actual device for a variety of other reasons.
You may be linking to lib that is non-existent on device, for example aygshell.dll or ccrtrtti.lib
You may be exporting function ordinal not present in core.dll of this windows build (try ExecutabilityCheck.exe for this; this free little program will tell which functions are missing http://www.hpcfactor.com/downloads/details.asp?r=40A26F4C-E4AC-41C9-81A1-1D81B4C41A0E)
Check linker command line, for one old project that I was involved in, and it worked ok on windows mobile 4 up to 6.5 I've had this "/subsystem:windowsce,4.02 /machine:ARM"
ARM v4 will generate code that will run, but you may hit problems with the SDK you use, and further problems when you come to debug. I'd recommend moving to Visual Studio 2008. (Not VS2010 because it doesn't include native Windows mobile development).