I have a really weird Xamarin.Forms bug I haven't seen before: When I build and deploy to simulator or device from Visual Studio 2017 on my PC the result is not aligned with the source code. What I see is some older build.
If I build from the same branch directly with VS2017 on the Mac instead I get the expected result.
Could this be some caching issue with the Mac Build Agent? If so; is there a way to clear it to ensure it doesn't deploy older builds?
[EDIT 1]
I have taken all the usual dark-magic tricks such as removing/restoring all packages, cleaning the output folders and reboot the Mac before rebuilding the solution. I also made 100% sure I wasn't using old source code.
Kindly,
Clean the solution,
Uninstall the app on the emulator.
Close VS
Rename the OBJ folder in the project folder (same place you have the
bin folder) to OBJ.old (in case you need to restore it)
Repeat step 4 for BIN folder
Restart the VS and open open the project
REBUILD the SOLUTION - you should have BIN and OBJ created for all projects.
Done
Related
I can't find any solution to this problem.
I had built my project in Release mode. When I changed to Debug mode and tried to rebuild the project, I got this error. And I KEEP getting this error no matter what I do.
I cleaned the project. No joy.
Restarted VS2019. No joy.
Deleted the bin and obj folders. No joy.
Switched back to Release mode. No joy.
The boss is waiting for this project and I can't build it because of this stupid unspecified error.
"...Another Xamarin operation is running..."
WHAT OPERATION???!!! How can I cancel that operation?
I rebooted the computer. No joy.
I own the paid version of Visual Studio Professional and this is not ok!!
Edit: I opened another version of the same project. This built ok.
Reopened the problem project and did not get the error.
Just wasted 2 hours on this
A workaround is :
Unload the Android project
Clean the solution
Reload the android project and restore it as Startup project
Now you can clean the solution and rebuild.
Unload the given project
Reload the given project
Clean the given project
Build
Solved.
Apart from restarting you may also need to delete bin and obj folders.
I had the same problem, but only on Android and not on UWP.
Edit: I opened another version of the same project on Android. This built not ok.
Reopened the problem project and did not get the error, so, problem solved.
Lots of thanks for your solution.
I started having this recently -- I use VS for Win connected to Mac to do the build for iOS project.
Let's face it, it's always wonky. But this got real bad today -- tried restarting VS, rebooting Mac, deleting bin/obj, etc.
Finally comment from OP made me think of something I didn't try -- shut down vs, delete the .vs folder, the bin/obj, and restart VS. I hate to delete the .vs cuz it resets stuff, including "reloading" my Android project, which I'm not currently working on.
Well, to early to say, but it worked once.
I'm having a weird problem...
I created a basic WinForms app in C# using Visual Studio 2013, and I added a Setup & Deployment project to the solution to build my .msi installer. For the Setup & Deployment Project's properties, I have the DetectNewerInstalledVersion to true, and the RemovePreviousVersions set to true. Then, with every build, I'll increment the version number and let Visual Studio change the ProductCode. Lastly, I'll make sure that the UpgradeCode stays the same.
In this configuration, if users run the .msi with a previous version installed, then it performs an upgrade. Everything works (as in all files are updated to the new versions, etc.). But, when they open Add/Remove Programs, the icon for the old version(s) is still there, as well as the icon for the new version.
For example, if they used the .msi to install MyApp version 1.1, then used the .msi to upgrade to 1.2, then again to 1.3, then MyApp will correctly update to version 1.3, but the user goes to uninstall it in Control Panel->Programs and Features->Uninstall a program, there will be three MyApp icons (one for each version). And to properly uninstall MyApp, they must right-click/uninstall all three. If I delete the old versions from the registry (the usual fix for stale icons), then MyApp will not uninstall correctly. The uninstall will go through the motions without error, but the program files and icons will remain, and the application will still function like normal. To troubleshoot, I've made a series of builds with sequential version numbers, then opened each build's .vdproj file in a text editor to ensure that the ProductCode and PackageCode have been updated, but the UpgradeCode remains the same. They do, so it's not a problem of the UpgradeCode changing. I've also tried deleting the registry keys for the old icons. This gets them out of the Programs and Features uninstall list, but it prevents the program from being properly uninstalled this way, so this isn't an option.
Anybody have any ideas?
This will happen when the first install is (say) Everyone and the upgrade is installed Just me (or vice versa). One type will not upgrade the other, so files will be replaced if installed to the same location, but there will be an entry for each in Programs&Features. They all must be Everyone or Just me to replace previous products.
You can install the upgrade with msiexec /I [path to msi file] /l*v [path to a log file] to see what's going on. If you search for occurrences of FindRelatedProducts you should see something about what it found and if it was the right context.
Note that Visual Studio setups can change the context if you do not have administrator privileges. You might specify an Everyone install but Visual Studio will change that to Just me if you don't have the privileges.
Ok. Weird...
The issue comes from the way that it's run. Once installed, the program checks the network share for a newer .msi, and if it detects one, it downloads it, then launches it with Process.Start and command-line args. The StartInfo.Arguments string looked like:
startInfo.Arguments = "/i \"[MSIPATH]\" /log \"[LOGPATH]\" TARGETDIR=\"[APPPATH]\" /qr+";
I guess someone fat-fingered the UI mode switch at the end. The "/qr+" switch should be "/qb!-". When I changed it, the problem stopped. I don't think that "/qr+" is even a valid switch, so I'm not sure why the install didn't just fail outright??? Anyway, that was the problem should anyone see something similar.
Special thanks to PhilDW for pointing me to the logs. :-)
I want to deploy my QT program and I can't find the reason it doesn't work, maybe you guys can help me ?
I work with visual studio 2010, windows 7, QT 5.0.2.
I have tested my deployment tree on my own computer and it works fine.
When deploying my application I ship every necessary dll that I am aware of. Depends.exe does not complain. I also deployed the plugin I know of, and since it still did not work I moved my entire plugin folder in the exe folder.
When I execute it on any other computer than my development computer, the program exits instantaneously with no message whatsoever.
Any idea where I should look now ?
How can I debug that kind of issue ?
Did you try deploying the debug version of the program and then starting it from the command line. The debug version will output more information to the console which could help you resolve the issue.
You will have to also deploy the debug versions of the MS c-runtime libraries.
Deploying the debug version is not a permanent solution, so you should not adopt that as normal routine for distributing your software. I am just suggesting that you try running the debug version one time on that particular machine until you figure out the issue. Then remove the installed program and install the release version again.
You can run your application using QtCreator:
Debug > Start Debugging > Start and Debug External Application...
This can give you more information about what's going on.
Hoping that I do this corectly.
I am having the above issue. My development machine is win7 64. Im developing x86 application,(x86 set in compile options). I have downloaded sqlite-netFx40-setup-bundle-x86-2010-1.0.81.0 as my app will be on .net4. I have referenced the above dll, set it to copy local. Can confirm that its in the deployed dirrectory. Tests OK on development machine both as a debug and a fully instaled app. When I put the app on a separate win 7 64bit it wount run due to the Dll. It installs ok into ProgramFiles(x86) and runs untill the database is required. The dll is in the instaled dirrectory when instaled on the other PC. (fresh win instal).
I am using InstalShield and it is also telling me about an error ' -6248: Could not find dependent file system.data.sqlite.dll, or one of its dependencies of component' but it compiles OK.
Im stearing at the Dll in the program , in the references, the intelisence picksup the SQLite name and all the code is right. I have referenced by browse and then finding the dll.
What on earth could I be doing wrong ?
This has had so many views that I decided to answer this so as to help others.
The problem isnt a big deal once you know what it is, despite the error message that sends you almost in the wrong dirrection. The problem isnt the DLL, its one of its dependancies. Basicaly you have to install C++ distributable file on the client machine , even if you are using VB.net. I cant take credit for the find, it comes from here http://justanothersoftwareengineer.blogspot.com.au/2011/08/how-to-make-systemdatasqlitedll-work-on.html.
I don't have much to go on... XCode 4 is hanging at startup with "Loading Project". My build fails but I can't access the errors. This is happening with a project that worked in a previous version of XCode. It also happens for new projects.
I had a simliar issue. I deleted project.xcworkspace and xcuserdata inside the .xcodeproj directory and I was able to open the project file.
Having the same issue at the moment, it was after pressing Continue a bunch of times on some internal logic errors. I think the .xcodeproj file is corrupted. Are you sure it won't even work on new projects?
My solution would be to delete it and create a new one, re-add all of the dependencies, build settings and existing source/resources, and then restart Xcode and try opening the project again. It should work this time. It has for me anyway.
Another issue could be if you're creating a new project on network storage and then it's somehow not loading all of the associated files because of a network error. Try moving the files to local storage if this is the case.
I had a similar issue which ended up being caused by a folder named "~" in my application resources directory. Deleting this directory resolved the hang.
I had the same issue, Xcode 4, after trying to add a framework and Xcode added everything under Xcode.app. It did not hang with the processing gear forever probably because my computer uses an SSD drive. After many minutes of the spinning gear, it was loaded and I removed the 'Reference' (right mouse click).