I'm trying to build my Xamarin.Forms project and running into an unexpected error "'cxmlns' is an undeclared prefix. Line 3, position 14". I've tried searching the web for a solution to this but not fining any. I've seen other similar problems and I tried solutions that worked for others, but nothing that worked in my case so far. Here is my MainPage.xaml code:
<?xml version="1.0" encoding="utf-8" ?>
<ContentPage xmlns="http://xamarin.com/schemas/2014/forms"
cxmlns:x="http://schemas.microsoft.com/winfx/2009/xaml"
xmlns:local="clr-namespace:DojoBoss"
x:Class="DojoBoss.MainPage"
BackgroundImage="background1">
</ContentPage>
I find it strange that I'm getting this error since this is all stock code that came with the blank app from Visual Studio (VS) aside from 1 line where I put in a background image. This was also working fine earlier today, I didn't make any changes but now it doesn't work. I've been disappointed with VS and Xamarin so far, seems very buggy and difficult to get started. Here's what I've tried so far:
Build project
Rebuild project
Clean project
Deselecting all projects from build (I have a main project + Android and Windows projects), applying changes, cleaning, building, re-selecting all projects to build multiple times in different orders.
Deleting bin and obj folders
Reopening VS multiple times
Deleting .vs folder, including the .suo file
Removing the line of code where error is thrown
Checking the build order
VS is also giving me 4 other errors which may be related to the problem:
Error CS0006 Metadata file 'C:\Users...\bin\Debug\netstandard2.0\DojoBoss.dll' could not be found
The "ResolveLibraryProjectImports" task failed unexpectedly.
Cannot resolve Assembly or Windows Metadata file 'C:\Users...\bin\Debug\netstandard2.0\DojoBoss.dll'
The name ‘InitializeComponent’ does not exist in the current context
I do not know what is this "cxmlns". Can we change this line
cxmlns:x="http://schemas.microsoft.com/winfx/2009/xaml"
to
xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml"
Related
I am trying to simply upgrade the version of vue3 we are running at work from v3.2.31 to v3.2.40. However, when I do, I am now getting an error in the runtime-dom.d.ts
Below is a screen shot from the file with vue v3.2.31 installed.
Once I've run the "npm update vue --save" command, the file looks like this (v3.2.40)...
...and VS 2022 throws the following error when trying to build...
If I delete the line from my local copy of runtime-dom.d.ts, all works as before. My problem comes when deploying the solution to the development environment etc. The npm install step puts a version of the runtime-dom.d.ts that does still have this line.
I'd like to fix this without having to resort to hacking the runtime-dom.d.ts file if at all possible.
Many thanks in advance.
I'm using Resharper inspect CLI tool for static code analysis(JetBrains.ReSharper.CommandLineTools.2018.3.1\InspectCode.exe) on a dotnet core 2.1 console application I've created. Within the solution, there is a separate project which is just a package used in the console app.
Layout is as follows:
When I run the inspectCode.exe as follows:
JetBrains.ReSharper.CommandLineTools.2018.3.1\InspectCode.exe "AI.DL.Backup\AI.DL.Backup.csproj" /o:"CodeInspection_20222.xml" /profile:"AI.DL.Backup.sln.DotSettings"
I get the following issue:
Output xml report has the following:
<IssueType WikiUrl="https://www.jetbrains.com/resharperplatform/help?Keyword=RedundantNameQualifier" Severity="WARNING" Description="Redundant name qualifier" CategoryId="CodeRedundancy" Category="Redundancies in Code" Id="RedundantNameQualifier"/>
<Issue Message="Qualifier is redundant" Line="5" Offset="146-154" File="AI.DL.Backup\src\AI.DL.Backup\Startup.cs" TypeId="RedundantNameQualifier"/>
The problem seems to be that it cannot find the dll project referenced and is throwing code analysis error (code HAS been built already, so bin/obj folders exist with relevant dlls/packages required).
Ling 5 (as specified) is just the using statement for the separate package, which it cannot resolve and is deeming to be redundant.
using AI.DL.DocumentManagement;
using AI.DL.DocumentManagement.Stores;
Going by the generated XML report, I can see that it can't find the namespace within the separate package. Why would this be? Anyone seen this before?
I was able to work around this issue when I repointed the "inspect.exe" to my solution file instead of individual project!
I am trying to build PhantomJS 2.0 on Windows from the c:\fastio\phantomjs\phantomjs directory. For some reason, the build process fails after a while, with 2 errors (see error message below):
1) It tries to access "C:fastiophantomjsphantomjssrcqtqtbasebinmoc.exe". Obviously, the backslash characters between directory names are somehow getting stripped away deep in the build process - possibly a mismatch between Windows-style "\" and Linux-style "/" (but this is only a guess).
2) There's another error, "Failed to read names from file: C:/fastio/phantomjs/phantomjs/src/qt/qtwebkit/Source/WebCore/mathml/mathtags.in".
If I remove sh.exe from the PATH, the build still gets to this point, and only error #2 appears, leading me to think that error #2 is the real problem here.
Here is the full error message (as far as I can tell this is happening while building WebKit):
sh: C:fastiophantomjsphantomjssrcqtqtbasebinmoc.exe: command not found
Failed to read names from file: C:/fastio/phantomjs/phantomjs/src/qt/qtwebkit/Source/WebCore/mathml/mathtags.in at C:/fastio/phantomjs/phantomjs/src/qt/qtwebkit/Source/WebCore/dom/make_names.pl line 315.
NMAKE : fatal error U1077: 'C:\Users\Eugene\AppData\Local\GitHub\PortableGit_c2ba306e536fdf878271f7fe636a147ff37326ad\bin\perl.EXE' : return code '0x7f'
Stop.
(By the way, I saw this question but I'm already past the issues described there, my error is happening later in the build process.)
How can I make this work?
Full logs below:
Console output:
http://pastebin.com/btMeNPz4
QT build log file build_qt_4-285-20-0859.log:
http://pastebin.com/LUEJz7E0
WebKit build log file build_webkit_4-285-20_0859.log:
http://pastebin.com/494TivXF
PhantomJS build log file build_phantomjs_4-285-20_0859.log:
Empty
Looks like I found the solution myself, here were my steps:
Remove as much as possible from the PATH leaving only the entries critical to the build process
Most importantly, remove all GitHub's git directories from the PATH
Install GIT separately (not from GitHub but from git-scm.com), add its cmd directory only (not its bin directory) to the PATH
Install ActivePerl separately, add it to the PATH
It's moving past the error I asked about with the steps above (still not sure if it will finish the build successfully, it's taking a while).
The last time I had my Windows Store app open (last night), I had a XAML error in it. I (tried to) open it tonight to try to fix it, but got all kinds of errors about things not being able to be loaded. Here are the important excerpts from the ActivityLog.xml file:
460
2014/12/25 01:39:17.198
Error
VisualStudio
SetSite failed for package [LocalHistoryPackage]
{3A6E8827-8C64-42EC-B83A-9CA32DA7BBF5}
80131500
No exports were found that match the constraint:
ContractName Microsoft.VisualStudio.Text.ITextDocumentFactoryService
RequiredTypeIdentity Microsoft.VisualStudio.Text.ITextDocumentFactoryService
. . .
935
2014/12/25 01:43:39.091
Error
VisualStudio
SetSite failed for package [LocalHistoryPackage]
{3A6E8827-8C64-42EC-B83A-9CA32DA7BBF5}
80131500
No exports were found that match the constraint:
ContractName
Microsoft.VisualStudio.Text.ITextDocumentFactoryService
RequiredTypeIdentity
Microsoft.VisualStudio.Text.ITextDocumentFactoryService
. . .
937
2014/12/25 01:43:39.092
Warning
VisualStudio
Package failed to load; error message suppressed by skip flag
{3A6E8827-8C64-42EC-B83A-9CA32DA7BBF5}
. . .
966
2014/12/25 01:43:52.147
Error
VisualStudio
SetSite failed for package [Microsoft.VisualStudio.Editor.Implementation.EditorPackage]
{E269B994-EF71-4CE0-8BCD-581C217372E8}
80131500
No exports were found that match the constraint:
ContractName
Microsoft.VisualStudio.Utilities.IContentTypeRegistryService
RequiredTypeIdentity
Microsoft.VisualStudio.Utilities.IContentTypeRegistryService
I shut VS down, reopened it and the project and, although I didn't see all those err msgs, and the project was ostensibly open, there was nothing in the Solution Explorer (no files displayed). I tried opening MainPage via File > Open, but that just resulted in another err msg.
The only other thing that changed the last time I had the project open was that I updated SQLite from version 3.8.7.1 to 3.8.7.2
What could be the solution (no pun intended)?
UPDATE
On trying to shut down Visual Studio, I got over and over again: "No exports were found that match the constraint...(bla bla bla)" until I had to stop it via Ctrl+Alt+Del
UPDATE 2
Here's what's even more bizarre: I can open the project and, although Solution Explorer is completely empty/no files
visible, if I build the project via Ctrl+Shift+B, it does give me the errors in the Error List (XAML errors in MainPage.xaml).
2-clicking them brings up nothing in the editor, though.
If I try to open MainPage.xaml, I get this:
But, although I just saved this file (the screen shot above), the date on it is 10/19/2014 - more than two months in the past. What the...?!?
What must I do to get this back to normal?
UPDATE 3
I do see this with the Team Explorer tab open (this app is not under version control):
Page '3185ed96-1cbd-4381-a439-636973542e50' not found.
I fixed the XAML issue by opening MainPage.xaml in Notepad ++ and changing the XAML around. I was then able to successfully build the app in Visual Studio, but trying to run the app caused VS to crash and then start up again (still with no files in Solution Explorer).
UPDATE 4
Now I get, "Package Designer Package failed to load" when I try to open MainPage.xaml via File > Open in VS 2013...
UPDATE 5
Now I can run the app (sort of); F5 causes the splash screen to display, and then it just goes gray-black. When I Alt+F4 to shut that down, VS starts back up again (apparently after shutting down - I intended to only shut down my running app, not Visual Studio.
AutoHistory tells me:
An exception was encountered while constructing the content of this frame. This information is also logged in "C:\Users\Clay\AppData\Roaming\Microsoft\VisualStudio\12.0\ActivityLog.xml".
Exception details:
System.Exception: Exception of type 'System.Exception' was thrown.
at Microsoft.VisualStudio.Shell.Interop.IVsShell5.LoadPackageWithContext(Guid& packageGuid, Int32 reason, Guid&
context)
at Microsoft.VisualStudio.Platform.WindowManagement.WindowFrame.GetPackage()
at Microsoft.VisualStudio.Platform.WindowManagement.WindowFrame.ConstructContent()
Anyway, I then notice that I do have a (literal) red flag, and mashing it shows me an "Renew your developer license" message.
I was able to update my dev license, but my solution is still wacky in the same ways as before.
UPDATE 6
Answering Walt Ritscher, I get this in AutoHistory on starting VS (no solution opened):
An exception was encountered while constructing the content of this frame. This information is also logged in "C:\Users\Clay\AppData\Roaming\Microsoft\VisualStudio\12.0\ActivityLog.xml".
Exception details:
System.Exception: Exception of type 'System.Exception' was thrown.
at Microsoft.VisualStudio.Shell.Interop.IVsShell5.LoadPackageWithContext(Guid& packageGuid, Int32 reason, Guid& context)
at Microsoft.VisualStudio.Platform.WindowManagement.WindowFrame.GetPackage()
at Microsoft.VisualStudio.Platform.WindowManagement.WindowFrame.ConstructContent()
Then, when opening another project that was working fine the last time I had it open, it, too, shows no files in the Solution Explorer. If I try to run it, I get that same "No exports were found" err msg.
So VS itself is hosed, it seems. What need I do? Uninstall/reinstall?
It seems likely that your VS install is hosed. You can try a repair first, before doing a reinstall.
last week I have faced the similar problem with my Visual Studio . I think these problems occurs due to the Pc Cleaners/Pc problem fixer and others like that. I just reinstalled the windows and visual studio and the same code executed fine.
So VS itself is hosed, it seems. What need I do? Uninstall/reinstall?
I would definitely try that. However, first I would copy the project to another machine with VS installed and try there. If it works on another machine then there is a problem on the first machine, possibly VS, possibly some extension or add-in. If it doesn't work on another machine then there is a problem with the code.
I'm trying to deploy an ASP MVC project developed on Mono/OSX on my Linux server using mono 2.10.8.1 w/ fastcgi-mono-server4
The webapp always starts fine, but then I start getting random CS0006 compilation errors for various URIs, and once they break, they remain broken until I restart the server application.
An example error:
Server Error in '/' Application
Compilation Error
Description: Error compiling a resource required to service this request. Review your source file and modify it to fix this error.
Compiler Error Message: CS0006: Metadata file `/tmp/root-temp-aspnet-0/ed68754/App_global.asax_40e709ea.dll' could not be found
~/Views/Order/Download.aspx
There is a related thread from January, but both the question and the answer seem to be mod_mono specific and rather hand-wavy. Anyone have any advice on what to try to debug/solve/work around this issue? It's getting very frustrating. In particular, is there any "unsupported" workaround where I can copy something from my Windows Server machines to use an MS implementation instead of the buggy mono one?
(I've filed a bug report too.)
Since the errors appear to be issue with the Mono JIT attempting to compile temporary files that don't exist, I spent a few days trying different methods of working around this issue (vs solving it). One solution that worked was using aspnet_compiler on Windows to create a binary version that could be copied and run as-is on Linux/Mono (as the latest versions of Mono now support precompiled ASP.NET applications).
However, I was looking for a native Linux solution, and I don't want to have to compile and sync binaries (vs syncing a GIT repo of code) to the server, so I was looking for another solution when I came across Mono ahead of time compilation, which is pretty much the equivalent of ngen.exe on Windows.
While it doesn't precompile everything, it seems to have done the trick. For me, this deployment script does the job without any runtime build failures:
xbuild SystemDiscs.sln
mono --aot -O=all SystemDiscs/bin/SystemDiscs*.dll
killall -9 mono
nohup fastcgi-mono-server4 /socket=tcp:127.0.0.1:8000 /applications=/:/var/asp/S
ystemDiscs/SystemDiscs/ > /var/log/systemdiscs.log &
Where SystemDiscs*.dll is the output of the solution compiled with xbuild in the first step. I don't think this precompiles the ASP pages (and --aot=full isn't supported on x86, as far as I can tell), but somehow it did the job. I was waiting to see whether or not that was just a fluke, but it's been going fine with maybe a dozen commits/deploys since I asked this ten days ago, so I reckon its safe to say it works.
I had a similiar problem:
Compilation Error
Description: Error compiling a resource required to service this request. Review your source file and modify it to fix this error.
Compiler Error Message: CS0006: Metadata file `/tmp/<DOMAIN/>/<username/>-temp-aspnet-0/5ed74d00/App_global.asax_34cccb99.dll' could not be found
/Default.aspx
But it didn't have anything to do with precompiling but with a backslash in my username. I use likewise-open to login to a windows domain, so my username is <DOMAIN/>\<username/> while my home-directory is without a backslash: /home/likewise-open/<DOMAIN/>/<username/>. This difference or just the backslash itself caused mono not finding the compiled global.asax in the temp directory. If you look closely to the detailed output you see that the backslash \ in the out parameter is changed to a forward slash /:
dmcs /target:library /lib:"/home/likewise-open/<DOMAIN/>/<username/>/Documents/test9999/test9999/bin" /debug+ /optimize- /warn:4 /out:"/tmp/<DOMAIN/>\<username/>-temp-aspnet-0/5ed74d00/App_Web_17ca7bdd.dll" /r:"/usr/lib/mono/4.0/mscorlib.dll" /r:"/usr/lib/mono/gac/Microsoft.CSharp/4.0.0.0__b03f5f7f11d50a3a/Microsoft.CSharp.dll" /r:"/usr/lib/mono/gac/System/4.0.0.0__b77a5c561934e089/System.dll" /r:"/usr/lib/mono/gac/System.Configuration/4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll" /r:"/usr/lib/mono/gac/System.Web/4.0.0.0__b03f5f7f11d50a3a/System.Web.dll" /r:"/usr/lib/mono/gac/System.Data/4.0.0.0__b77a5c561934e089/System.Data.dll" /r:"/usr/lib/mono/gac/System.Web.Services/4.0.0.0__b03f5f7f11d50a3a/System.Web.Services.dll" /r:"/usr/lib/mono/gac/System.Xml/4.0.0.0__b77a5c561934e089/System.Xml.dll" /r:"/usr/lib/mono/gac/System.Drawing/4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll" /r:"/usr/lib/mono/gac/System.EnterpriseServices/4.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll" /r:"/usr/lib/mono/gac/System.IdentityModel/4.0.0.0__b77a5c561934e089/System.IdentityModel.dll" /r:"/usr/lib/mono/gac/System.Runtime.Serialization/4.0.0.0__b77a5c561934e089/System.Runtime.Serialization.dll" /r:"/usr/lib/mono/gac/System.Xaml/4.0.0.0__b77a5c561934e089/System.Xaml.dll" /r:"/usr/lib/mono/gac/System.ServiceModel/4.0.0.0__b77a5c561934e089/System.ServiceModel.dll" /r:"/usr/lib/mono/gac/System.ServiceModel.Web/4.0.0.0__31bf3856ad364e35/System.ServiceModel.Web.dll" /r:"/usr/lib/mono/gac/System.Core/4.0.0.0__b77a5c561934e089/System.Core.dll" /r:"/usr/lib/mono/gac/System.Web.Extensions/4.0.0.0__31bf3856ad364e35/System.Web.Extensions.dll" /r:"/usr/lib/mono/gac/System.Data.DataSetExtensions/4.0.0.0__b77a5c561934e089/System.Data.DataSetExtensions.dll" /r:"/usr/lib/mono/gac/System.Xml.Linq/4.0.0.0__b77a5c561934e089/System.Xml.Linq.dll" /r:"/usr/lib/mono/gac/System.ComponentModel.DataAnnotations/4.0.0.0__31bf3856ad364e35/System.ComponentModel.DataAnnotations.dll" /r:"/usr/lib/mono/gac/System.Web.DynamicData/4.0.0.0__31bf3856ad364e35/System.Web.DynamicData.dll" /r:"/usr/lib/mono/gac/System.Data.Linq/4.0.0.0__b77a5c561934e089/System.Data.Linq.dll" /r:"/usr/lib/mono/gac/System.Web.ApplicationServices/4.0.0.0__31bf3856ad364e35/System.Web.ApplicationServices.dll" /r:"/home/likewise-open/<DOMAIN/>/<username/>/Documents/test9999/test9999/bin/test9999.dll" /r:"/tmp/<domain/>/<username/>-temp-aspnet-0/5ed74d00/App_global.asax_34cccb99.dll" /nowarn:0169 /d:DEBUG -- "/tmp/<DOMAIN/>\<username/>-temp-aspnet-0/5ed74d00/App_Web_17ca7bdd_0.cs"
So:
/out:"/tmp/<DOMAIN/>\<username/>-temp-aspnet-0/5ed74d00/App_Web_17ca7bdd.dll
becomes
/tmp/<DOMAIN/>/<username/>-temp-aspnet-0/5ed74d00/App_global.asax_34cccb99.dll
If I copy the directory 5ed74d00 to /tmp/<DOMAIN/>/<username/>-temp-aspnet-0/ the application works as expected.
It took me almost 2 days to see this, so hopefully I can help others with this answer.