I am starting maui app in Visual Studio using button "Windows Machine" and the result is on the picture that I connetced. Is it a problem in Visual Studio? I asked my college to check an app on his pc and he showed me that it wors and launches without hanging...
I tried to change text property of the area it works perfectly
You can try the steps below:
open Computer Settings→ select Privacy & Security→ select Turn on developer mode.
downloads for the Windows App SDK.
delete the 'bin' and 'obj' folders, rebuild and run your project.
Related
Our company has a native iOS app that was built in Xamarin/Visual Studio. We originally uploaded it to the App Store a few years ago and have made a few changes to it over the years.
The app itself is very basic. It's basically just a web view that navigates to a Single Page Application. There is very little native app code in the project.
Every week or so I regular launch the native app on our company iPad. Instead of running a version pulled down from the App Store, I periodically rebuild and upload the app from a Mac Mini running Visual Studio and/or debug it directly from the Mac Mini through Visual Studio.
A few days ago I tried launching the native app and after opening it immediately closed. I tried rebooting the iPad but the app still minimizes/closes immediately after opening. If I double-tab the Home button on the iPad, I can see the app still running in the background, but any time I tap on it it immediately minimizes itself.
I tried Cleaning and Rebuilding the native app solution in Visual Studio and re-uploading it to the iPad and that didn't fix it. I updated Visual Studio (and all of its packages) on the Mac Mini, updated XCode, updated Mac OS, updated iOS on the iPad, and nothing resolved the issue.
When I attempt to debug the app from Visual Studio, it shows two error codes in the Output window: MT1043 and MT1007. The debugger always fails to attach to the app as well.
I've tried Googling the error codes and the problem itself and haven't found anything that has worked. I've tried generating a new Development Certificate and Provisioning Profile to use to sign the app when uploading it to the iPad but that didn't work either.
What's strange is that if I download the app off of the App Store it works just fine. The source code that I'm attempting to build/run right now is identical to what it was at the time it was deployed to the app store. What else is strange is that, if I spin up an iOS Emulator and upload/debug against that, the app works just fine.
I tried using a different iPad and it had the same issue. The app minimizes itself immediately after attempting to launch it.
Found the answer. Had to set the system certificate trust from "Always Trust" to "Use System Default". Same solution as provided here: https://stackoverflow.com/a/52506186/9704484
I'm creating apps by VS 2015.
My Project is made by UWP. I know this is for Windows Store Apps.
however, My Project is LOB Side Loading.
I compiled and packaged my project, and then I moved to all of files to other computer.
then,
I Set 'Developer mode' in Control Panel.
I executed 'Set-ExecutionPolicy RemoteSigned' in PowerShell.
then i excuted 'Add-AppDevPackage.ps1', then my app installed successfully.
However, I found my app in start menu, but I couldn't click that !!
I couldn't launch that.
How can I do to launch my uwp app in other computer?
I'm doing an app using Xamarin.Forms and I've already deployed the Android and iOS version to HockeyApp but I have a problem with the UWP (Windows 10 version)...
These are the steps I do:
Right click on my UWP project
Select "Store" option
Select "Create app packages"
A window pops and I select "No" and click "Next"
Then I only select the ARM configuration
Click "Next"
My package has been created and I drag n drop the .appxbundle file to hockeyapp.
Once the package is uploaded, I start my Windows 10 Mobile emulator and try to install it...
I download it from HockeyApp and when I install it, nothing happens...
Do you have any idea where this problem comes from?
I'm using Visual Studio 2015.
Windows 10 mobile emulator not supported ARM, only x86/x64. You need the real device for test ARM package.
I was experiencing exactly the same, but I've managed to fix it. Here's what I've done:
I associated the app with Store in Visual Studio
I installed Windows 10 Mobile Anniversary update (OS Build: 10.0.14383.953), since my app was targeting Anniversary Update.
I installed the certificate which was included in the .ZIP file next to the .appxbudnle
Then I run the .appxbundle and clicked install. The installer exited without any message, just like before, but after a minute or so the app appeared in the installed apps on my Microsoft Lumia 650.
I am developing a wpf app. I want to publish my app to Windows tablet.
These were the steps I did:
Right click on project
Click publish
Provide a path to publish
Then it has generated files to install – I have tried to install the generated manifest file in both published machine and tablet. I can see my app in "add/remove", but when I open the app from the Start menu my app is not initiated. It's not displaying anything.
Thanks,
Punith
Everything works if I do "Attach To Process".
But I need to debug a problem during launch of an application, so I need to be able to either "Start project" or "Start external program" the remote exe.
When I do, I get "directory does not exist". (Presumably, It is either looking for this non-existent directory LOCALLY, or it lacks permissions.)
Details:
* .Net Framework 3.5; C# Windows Form, with button that when clicked does
Debug.WriteLine("Hello World!");
Two Windows 7 Ultimate PCs, with same username and password, administrator.
Local PC:
Visual Studio 2010 Professional. Hello World project open and built.
Tested locally: Start Debugging / hit button / see "Hello World!" in VS Output pane.
Quit local version of app.
Remote PC:
Visual "Microsoft Visual C++ 2010 SP1 Redistributable" installed (so can run a debug version of this .Net application; before installing said "The program can't start because MSVCR100.dll is missing, when hit a breakpoint.").
Visual Studio Remote Debugging Monitor running.
says "(date/time) Msvsmon started a new server named Steve#FRESHINSTALL: Waiting for new connections".
When Attach to Process, says "FreshInstall\Steve connected".
Copy from local pc's project location (in default VS 2010 projects), \bin\debug* to C:\Code\HelloWorld*
Code folder is Shared with full privileges (just in case ...)
Attach to Process works fine:
click button => "Hello World" -- in Local PC's Output pane, just like when running locally.
Now, the problem. How LAUNCH the .exe remotely, instead of Attach to Process?
On Debug pane:
Tried "Start project"
alternatively, tried "Start external program:" C:\Code\HelloWorld\HelloWorld.exe" -- on Remote PC, this is the path to .exe
Working directory: "C:\Code\HelloWorld" <-- this directory ONLY exists on Remote PC (deliberately -- to make sure we aren't executing locally)
[checkmark] Use remote machine: FRESHINSTALL.
Tried with and without "Enable the Visual Studio hosting process".
When do "Start Debugging", all variations say "The working directory does not exist: "C:\Code\HelloWorld".
Well, of course not: it is on Remote PC, not locally.
Yet everywhere I look, this is what instructions say to do.
What am I supposed to do differently, or what could be wrong?
(Obviously this simple app, I could stick with Attach To Process. But I have a MUCH more complicated multiple-dll application, which is having a problem during startup. I need to breakpoint the "real" application during its start up, not after it is already running.)
(And the real situation I have to debug, is on the other side of the world, with a slow internet link. This is a local simulation of what is going wrong there. Not practical to install visual studio on the actual remote PC, to turn it into a local debugging situation. Spent a day trying to remote debug that; after I get it working on a local network, I have to duplicate the whole process with much less control over what is going on.)
In the interests of closing this question, to indicate that it has been addressed:
See wal's first comment on my question, and follow the link he gave, which I repeat here:
Visual Studio remote upload and debugging on other computer