I've just installed the MahApps from GitHub
https://github.com/MahApps/MahApps.Metro
I'm getting errors immediately. In MainWindow.xaml the following line is underlined
d:DataContext="{d:DesignInstance MetroDemo:MainWindowViewModel}
And there are several error messages, such as:
The name "MainWindowViewModel" does not exist in the namespace "cld-namespace:MetroDemo".
The name "ButtonsExample" does not exist in the namespace "clr-namespace:MetroDemo.ExampleViews".
The project does run, but I'm unable to inspect any of the design.
Has anyone experienced this and managed to resolve?
Turns out this was to do with Parallels on my Mac.
Issue found here, with resolution from Mick MacCallum.
The issue with the namespaces was due to VS using network share to access the files on my Mac file system.
I copied the entire project over to the absolute path on the virtual machine and the problem was solved.
The project now builds/runs correctly but I can also inspect the design.
Related
I've recently been asked whether it was possible for me to convert my older theme contributions to the new Qooxdoo packaging system. So I installed Qooxdoo 6.0 and got a first test app running - not without problems because the instructions in the official docs are a bit buggy (e.g "npx qx" is an unknown command with my Ubuntu 18.04). I also read about the packaging system and what to do to install one of the existing packages from the Qooxdoo repository.
Then I followed the steps described in section "Create a new package". This procedure resulted in a folder structure which looked familiar at first sight, but a closer look made me wonder: There are two resource folders now, one is under "source" (as I would have expected) and the other one is under "source/class/[mypackage]". I also noticed that there is a "demo" folder in "source/class/[mypackage]", which used to be a top-level folder in previous Qooxdoo versions.
I then copied the theming files of my contribution to "source/class/theme", the demo app files to "source/class/[mypackage]/demo" and the demo resources to "source/class/[mypackage]/resource". After compiling the project I managed to run the demo app, but only without the expected resources (no icons, no fonts, no background images). The theming as such appears to be applied properly, but I keep getting plenty of error messages telling me "404 (Not found)" and "Image could not be loaded".
What am I doing wrong?
I guess you are running into a bug with our template for packages ... please open an issue https://github.com/qooxdoo/qooxdoo-compiler/issues/
As for how to do it. Have a look at an actual theme package for 6.0 https://github.com/ITISFoundation/qx-osparc-theme there you can see the required structure.
Also, for this kind of question, interactive help is probably best. Visit the qooxdoo chat on https://gitter.im/qooxdoo/qooxdoo
In most of the Helix 3d wpf examples (source files) posted in GitHub, there is a reference to "Example Browser" (using ExampleBrowser;) in the .cs files. I cannot find any assembly defining a reference to this namespace in the packages obtained from Nuget (HelixToolkit and HelixToolkit.Wpf). I commented this line out and solution builds OK and app runs OK.
Anyone has any idea where this line comes from or where the assembly is?
Thanks in advance.
ikonuk
If you clone the repo of helix-toolkit you'll see that in the Helix-Toolkit solution there is a separate project called example browser for showcasing various use cases. Nuget packages only contain the helix-toolkit itself without the examples
I moved my RCP application from Eclipse Oxygen to Photon, and also from Java 8 to Java 10.
The code compiles and the application works fine if I start it from Eclipse. However, when I try to build my application, I get an error:
plug-in JavaSE_0.0.0 has not been found
Missing Constraint: Bundle-RequiredExecutionEnvironment: JavaSE-10
Host plug-in JavaSE_0.0.0 has not been found.
I can't find any useful solution on Google. Maybe some of you can help me.
My manifest file contains this header:
Bundle-RequiredExecutionEnvironment: JavaSE-10
This seems to be an Eclipse bug. Eclipse seems not to able to deal with JavaSE-10 properly.
The simplest solution at the moment is just to use Bundle-RequiredExecutionEnvironment: JavaSE-9 rather than JavaSE-10 and put up with the warning that this doesn't match the JRE container.
Since OSGi 4.3, the most appropriate way to specify a minimum Java version is using the Required-Capability header, as in:
Require-Capability: osgi.ee;filter:="(&(osgi.ee=JavaSE)(version>=1.10))"
I have had success fixing the reported error by replacing all occurrences of Bundle-RequiredExecutionEnvironment with the above line. In PDE, you may get a warning on the manifest file, but it can be safely ignored. Product validation and product exports seems to work without issue. One thing I'm not sure however is how P2 reacts when fed bundles that do not contains the BREE header.
Alternatively, Eclipse 2018-09 is now out, and seems to provide a JavaSE-10 environment description (just in time for JavaSE 10 deprecation...); I haven't tested yet JavaSE 11 support (available as a plugin for Eclipse 2018-09).
I'm not sure what happened here but I was always able to publish to my local pc for my ExtJs project. Now all of a sudden I am getting this error..
Error Copying file Sencha.sencha\app\app.defaults.json to obj\Release\Package\PackageTmp\Sencha.sencha\app\app.defaults.json failed. Could not find a part of the path 'Sencha.sencha\app\app.defaults.json'. ExtApplication4 0
I think I did upgrade version of ExtJs a while back but not sure this is what caused it.
I also notice the files don't exist when I look at solution explorer.
Any ideas? This is pretty vital to my whole situation.
Did you upgrade Sencha Cmd to 6.5x? This new version does not create the .sencha hidden folder anymore. You error seems to be related to this.
When I am trying to build a solution file which has WPF projects, I get this error
Could not copy the file "bin\Debug\test.exe.config" because it was not
found.
I tried Clean Solution, Rebuild solution. Tried deleting the bin directory. This started yesterday. Not sure what I changed.
How do I fix this. so I can do a build.
Just a thought, but anti-virus software could potentially cause this type of problem if it decides that your exe is suspicious.
If you have any AV software running, try disabling it temporarily, and/or excluding your project build folders from its protection.
OK. The problem with my solution was a extension(a config Transform extension) that was installed. I updated the Visual studio extension and the build succeeded.