I understand .NET 7 is new, but I think a workflow that should work out-of-the-box is to create a new MAUI template project (".NET MAUI App"), choose a name for that, and successfully build the just-created project. On my system, this consistently fails with this warning:
Severity Code Description Project File Line Suppression State
Warning XA1004 File 'obj\Debug\net7.0-android\lp\101\jl\res\..\res.zip' already exists. Ch0501 C:\Program Files\dotnet\packs\Microsoft.Android.Sdk.Windows\33.0.4\tools\Xamarin.Android.EmbeddedResource.targets 36
While I do not like this warning on a brand-new project, there is another issue: I nothing happens when I launch the project by clicking Windows Machine:
For .NET 6, this would launch a "welcome" form, welcoming you to MAUI. Now, the program runs but then ends without presenting any UI.
How are users expected to get started with MAUI with issues like this? I will single-step and debug to try to see what's going on, but shouldn't this just work??
Does anyone familiar with .NET 7 MAUI know why I am encountering these issues? What do I need to do to run the app so that it displays the MainPage "welcome" form on Windows?
I decided that I don't have time for MAUI's broken-ness. I visited several devoted MAUI forums, and many users have complained about functionality that's broken out-of-the-box using the latest of all available IDEs, frameworks, and tooling. MAUI's bug list is ever-growing and outpaces the rate at which bugs are fixed (often needing further fixes due to lack of QA testing). The fact that my basic question about MAUI received a few dozen reads (as of this writing) and no useful reply suggests that broad understand of MAUI fundamentals does not yet exist in the developer community. I don't have time or interest in being an extension of MAUI's QA team and to work with tools whose "hello world" out-of-the-box sample cannot run on a new installation. It's just ridiculous.
I installed Uno 4 instead, and their "hello world" app ran without a hitch (using .NET 7) on Windows and on my tethered Android device. So I plan to use Uno for my multi-platform C#/.NET 7 project. Maybe in the distant future, MAUI will be ready to be reconsidered--for now, it's a pet project that desperately needs some professional attention.
Related
I just upgraded to IBM Mobile First (worklight) 7.1.0.00.20150913-2345.
I've noticed that my app now shows twice in Eclipse servers pane. Other services shows twice too. Is this normal or something in my configuration is causing it?
This is a recent regression that was introduced in MobileFirst Platform Foundation 7.1. It is harmless, but will be taken care of regardless...
If you so choose you can open a PMR (support ticket), but it is scheduled to be fixed regardless.
So I've been messing around with the packaging feature that NetBeans offers, following this tutorial: http://platform.netbeans.org/tutorials/nbm-nbi.html. I didn't like how I had to modify the platform that my IDE was running on in order to customize the installer itself, so I decided to create a copy and just change the platform the application suite was using (Properties->Libraries).
This seemed to work fine, and even packaged that platform as part of the installer. However, when doing the packaging itself, I noticed that it was calling the IDE's platform build script to create the installer rather than the one I had customized. This defeats the purpose, at least in my case, of having the separate platform.
Within the platform manager, under the harness tab, I made sure that the platforms harness was being used rather than the IDE's, but it didn't seem to make a difference.
I verified the behaviour by throwing an echo into both the default IDE platform and my customized platform to see which was being called. I also noticed that the Ant call that gets made at the start of packaging makes an explicit reference to the IDE platform, as well.
I've tried this under 7.2 (currently using 7.3) as 7.3 has had some fairly nasty bugs and thought perhaps it was just recently introduced.
At this point I'm thinking it's a bug, but I was hoping that perhaps someone else had come across this and found some sort of solution or could shed some light on why it's doing what it's doing.
Thanks!
This is slated to be fixed for 7.4, in case anyone comes across it in the meantime.
Here's a link to the bug ticket: https://netbeans.org/bugzilla/show_bug.cgi?id=229478
I post this merely as a reference for others that might end up being in the same situation and since I spent almost 3 days trying to figure out the root cause of the problem, I thought it would be a good idea to post the solution here.
My situation was as follows:
I tried to build a deployment package for a .net application and got TypeLoadExceptions, FileNotFoundExceptions (regarding DLLs), Side-By-Side configuration errors, etc. once I tried to run it on a vanilla test machine.
[edit]: stackoverflow won't let me answer my own question within 8 hours of it being posted, the answer follows in ~8 hours ;)
The problem was that one of the dependency projects of my application was set to "Debug" build in the Visual Studio configuration manager, therefore the debug dll of the dependency ended up being used for release builds as well. On any development machine this was no problem after all since all debug runtimes were available.
On the vanilla test machine however only the release runtimes were present which caused so much trouble to me and gave me unmeaning exceptions that lead me to so many wrong directions via google, etc.
In my case it was SlimDX that was set to build a debug build in the VS configuration manager, even when doing release builds. Since SlimDX makes use of the VC runtimes I got the above problem, but this could happen with any .net assembly that uses the VC runtimes.
I hope this will eventually safe someone some hours ;)
Friends Initially there was problem in the re installation of VS 2010 in my computer with Xp.
But i was able to install recently and every thing goes fine. I was able to use MVC 2 and other features. But when i tried to install MVC 3 i could not get success.THe installation process Roll back giving the message of FATAL ERROR DURING INSTALLATION.
Then i check in the error and found that Microsoft ASP.NET webpages 1.0 was missing in my computer.Is that the problem for installing MVC 3? or other .
I have attached the screen shot of error. I will be thankful for the solution.
Sorry, i couldn't upload clear picture.But Error shown was as follows:
Returning IDOK, InstallMessage_error[This product Requires Microsoft Asp.net web Pages 1.0. Please install the missing component, then try to install this product again.]
strong text
Using the Web Platform Installer will probably be the easiest way for you to solve your dependency installation problems. Using the installer will give you the ability to select and download/install a variety of products. For instance take a look at the follow screen shot:
Under the Products tab, you have the ability to select MVC3, ASP.NET web pages, MVC3 Updates, etc. Since some products depend upon others the Web Platform Installer will also manage these dependencies for you when installing your selected items.
Good luck, and hope this helps you some.
I'm working on some legacy code for a client, involving Microsoft Content Management System (MCMS).
Currently, everything is local, the code, MCMS, SQLServer, and IIS (5.x).
I copied the project folder, and then opened the new copied solution in VS2005, and let it do it's conversion thing.
But now nothing works. I've nnotice there have been some changes to IIS profile. What are the extent of these changes...??
Also, my VS2003 fails to recognize the Web Project??
Anyone have any idea what's going on?
cheers!
Not really sure the extent to which MCMS affects anything (since I have not used that tool) but as to the question on the VS2003 not recognizing the web project, the issue is that when Visual Studio 2005 does it's upgrade, it changes the format of the VS2003 project files to VS2005 format. This means that once you have upgraded a project to VS2005 you can't go back and open it using VS 2003.
As far as changes to the web project go -
VS 2005 by default completely changes the layout and mode of your web projects. If you want to retain the familiar (and IMO better) web application layout from VS 2003 you need to use the web application project option which is available as a download - details are here
Hope this helps.