I'm unable to run Coded UI Test Builder. I'm going to implement UI tests for the Windows Phone app. I'm using Visual Studio 2015 Enterprise and created simple test project and added Coded UI Test project. However, an error occurs during launch "Generate Code for Coded UI Tests...". Windows Phone 8.1 emulator is launched, but the error still occurs.
Also, I tried to launch standalone "codedUiTestBuilder.exe". It cannot recognize control in emulator at all. It recognizes only main window of the emulator, but nothing more.
Followed this manual, but it didn't help me.
So I ran into this issue also, what ended up fixing the problem was creating another Solution for my Coded UI Test Project. Separating it out from the App solution seemed to be a workaround for this problem.
I do not know what the underlying cause was.
Related
I've got a project that I am working on that works fine when debugging from IntelliJ but when I do a release build (still in IntelliJ) and install the .air fil to my computer none of the FastInject tags seem to work.
I thought that this might be due to the include-as3-metadata issue but that does not seem to be the case. I have included all the metadata tags that I think I have used.
I have spent some time investigating this and have not made much progress other than getting frustrated!
I created a view that displays the logs created by spicefactory - but this seemed to fix the issue!
I tested to see if I could inject and of classes that are expected to be FastInjected, this also fixed the issue.
It seems that if I add any logging related code to the application the FastInject tags start working.
In fact, I have created a release air file here. If I install this on a computer with Flash debugging turned on the application doesn't work. If I follow the steps here to debug an installed Air application - it starts to work!
If anyone else can confirm this behavior I would appreciate it.
It turns out that this was simply a race condition causing an error in context creation that was not displayed in a non-debug player.
This exception never happened while I was developing the application and any changes to the application to add logging changed the initialisation order of the context and caused the issue.
I'm having periodic issues with changes I make to a website I'm building with VS not showing up when I run the VS debugger. For example, sometimes if I delete a section of code it still appears when I run the code using the VS debugger. This issue doesn't happen that often, and seems to appear and disappear randomly. If I go into the project's folder and manually open (double-click) the .html page I'm working on I can see my changes, so I know it's an issue with VS.
Is there something obvious I'm missing? I've just started using VS for web development, and as far as I know I'm using all the default settings.
Thanks!
Clean and built your project and try again dude.
Recently I created an app that uses background agent and live tiles in it. The problem is - the application works perfectly when I straight away deploy the XAP file to device(or emulator) but when I download the same app from store, then the app exits without even navigating to MainPage.
Is this because of background agent or anything else, I don't know am totally confused in this. Can anybody please help with this?
If you're application uses a periodic Background Agent and you are testing it with the LaunchForTest method you should make sure that you are not calling this in your release build of the code.
Protect it with appropriate conditional compile time checks:
#if DEBUG
ScheduledActionService.LaunchForTest(periodicTaskName, TimeSpan.FromSeconds(1));
#endif
Note that DEBUG is defined by default in the "Debug" configuration and not in the "Release" one for situations such as this.
Answered by Matt Lacey - https://stackoverflow.com/a/15339129/1392194
I have a weird problem in an windows phone 8 project (Visual Studio Express for windows phone 8) that Changes to xaml( ex:change visibility of control) don't reflect on App until I rebuild the project and deploy it again to emulator or device.
The changes reflect normally in the design window of visual studio but didn't reflect on the running App.
I did many researches and they didn't help, like:
1- Change "Build and Run" to "always build" when projects are out of date.
2- I checked configuration manager as This post suggests but it was selected.
I have the exact same issue. I have a work around at the moment to save the hassle of rebuilding the solution because rebuilding deletes and re-installs the app and changes any saved settings you've made while debugging. The work around is to switch between configurations. So I'll execute the app in Debug, make some changes, then the next time I execute I change config to Release, and the changes are there.
The difference I can see is when it works I can see the Build Output line which says "Updating the application as the manifest file has changed..." take a few moments to complete. When this issue occurs the output line appears for a split second and so you can tell the incremental deployment hasn't actually been deployed to the device/emulator.
This is a little frustrating so hopefully someone has a real answer. I have other projects on the same machine and they don't have this issue. Just the one project so I don't think its a VS2012 problem.
I've also tried suggestions from other sites saying delete bin and obj folders but that didn't work.
I had the same issue for some of my WP8 Silverlight projects in VS 2013. I couldn't understand why it happened only for some projects but not all, but eventually I found this forum thread. The solution is the following: if the name of your app includes spaces, you definitely need to remove them or replace say with the underscore char. This recipe helped to recover my 'problem' projects.
I also noticed that numbers at the beginning of app name cause the same problem. I solved it by removing numbers from solution and app name.
For the sake of testing, knowing that I am running from Visual Studio would be nice. I could see if the debugger is attached, but that is not sufficient if I am running with CTRL+F5.
Here's how to see if the debugger is attached:
if (Debugger.IsAttached) Foo();
But my question is, I wonder if there is a way to ask if the current app is from the Store. So, I thought about install folder, but they are identical. Then I thought about this:
Windows.ApplicationModel.Package.Current.Id;
But this appears to be completely implemented even for apps that are being debugged. So, I am stumped. Does anyone know if we can determine if the app is from the Store?
While certainly not the most elegant solution and there's probably a better one, you can check Package.Current.InstalledLocation.Path
If you are running a debug build developed on your local machine and not side loaded, you'll have /debug/ in your folder path.
In Windows 10 apps (this also should be available in 8.1), you can check the IsDevelopmentMode property on the current package.
Package.Current.IsDevelopmentMode
That should tell you whether the package was installed in development mode (which I believe is synonymous with 'side-loaded').
See https://msdn.microsoft.com/en-us/library/windows/apps/windows.applicationmodel.package.isdevelopmentmode.aspx
for more information.