I am working on an mvvmcross solution. I am making a wpf project as well to speed up the core development. Today I ran into an issue running a wpf project using a core that has the network plugin. When the setup.Initialize() is called I end up with the exception "Could not load file or assembly 'Cirrious.MvvmCross.Plugins.Network.Wpf' or one of its dependencies. The system cannot find the file specified.". I did include the network plugin from NuGet to my wpf project as well. Anyone know what might be the issue here?
Thank you!
i only added the wpf version of that plugin 5 days ago - https://github.com/slodge/MvvmCross/commits/TibetBinding/Plugins/Cirrious/Network/Cirrious.MvvmCross.Plugins.Network.Wpf
It hasn't yet made it to nuget - when it will depends on my work schedule and my hotel wifi - 'soon' is all I can say.
You can build it for yourself if you need it urgently - on the tibetbinding branch (see link above)
Related
I have an eclipse codenameone project. I would like to execute this project on Eclipse using my own codenameone modified sources (codenameone sources project is in netbeans). How could I do that ?
As it is mentioned in this video, we should linked the project in the build path but it works only if we have a netbean project.
Better solution is to edit Codenameone source in Eclipse (but sources in github has structure of a Netbeans project).
Thanks!
Right now debugging with the Codename One sources is only supported on NetBeans because that is the platforms we use for our coding. It's harder to work with other IDE's and might not be worth your effort.
Someone posted a while back in the discussion forum about running this in Eclipse but I couldn't find the reference.
Generally if you want to build the native sources and debug from there just work based on the logic we have and adapt it to Eclipse (or any other IDE). Running a Codename One project has 2 major dependencies:
Codename One project - that's a regular Java project you can work with
JavaSEPort another regular project, this is the implementation of the Codename One code and includes the simulator.
Make sure to add the source trees of both these projects to the compile but not packaging phases and set the Simulator class as your main class.
If you are successful in doing this it would be really nice if you write about it for the developer guide wiki next to the NetBeans build and explain how this is done for future developers.
In my Silverlight solution I have a edsv project and a edsv.web project. If I make edsv the startup project it works ok. If I make edsv.web the startup project, it executes a much earlier version of the code.
The setup project need to use the .web project, right? So my install kit reflects the wrong code. How do I get the projects in sync?
I got the solution in another forum, please see http://social.msdn.microsoft.com/Forums/silverlight/en-US/8293acb7-a2dc-4c04-92f7-150830cc355a/how-to-sync-the-silverlight-and-web-project
Bob
How can I use it on WinRT (Windows 8) - I can't compile it. Can I use it also with "normal" Windows (WPF)?
There isn't currently an mvvmcross port specifically for wpf - a couple of people have suggested building one, but the majority of users have so far requested more work on mobile platforms instead. There is a current console (win32) port and extending that towards WPF should be quite straight-forward.
Future development is now based around the Portable Library branch - see some info on http://slodge.blogspot.co.uk/2012/09/mvvmcross-vnext-portable-class.html and the code on https://github.com/slodge/MvvmCross/tree/vnext
For WinRT, the TwitterSearch example within the vNext branch is a good place to start - it should compile and work across all of MonoTouch, MonoDroid, WP7, WinRT and Console:
If you find you can't compile then please log specific compiler error messages either here or to github issues.
MvvmCrossLibs\MvvmCrossLibs.sln consists of many projects, requiring different runtimes to be installed to open properly (Mono Touch, Mono Droid, WP7). If you only need the library in WinRT, your best bet is to open Cirrious\Cirrious.MvvmCross\Cirrious.MvvmCross.WinRT.csproj directly and add the missing Newtonsoft.JSON package with NuGet (you'll need to save the automatically created .sln file before that). It should compile just fine after that, at keast it did for me. Now just reference the assembly in your Windows Store app project and start using it.
I don't have any previous experience with MVVMCross, but it doesn't look like it currently supports despktop WPF apps. I don't know how difficult it would be to create/compile such a version, though.
Error. The type or namespace name 'GridViewExpressionColumn' could not be found (are you missing a using directive or an assembly reference?)
Hello all,
I've inherited a VisualStudio 2010, Silverlight 4 project with a custom RadControl from Telerik. The project runs fine on the server, but I would like to make some changes locally. When I copied the project folder over to my c drive, the application cannot compile (build errors). After cleaning the solution, I still keep running into CLS-compliant issues, and most notably, the error listed above. I'm not sure what the problem is, since I've never worked with Telerik or third party RadControls. Any help would be appriciated.
Thank you.
You will need to contact your office software guru and get a licensed copy of Telerik RadControls to install on your local development machine.
To get you compiling, for now, you can use the demo version available at http://www.telerik.com/support/demos/developer-tools-demos.aspx - any solutions compiled from this will show a big "DEMO" banner accross the control for a few seconds.
I've upgraded WPF application to Visual Studio 2k8. App is .NET 3.0 which is set as a platform in the project.
If I build project & release confiuguration, app is running well.
If I try to publish it using ClickOnce, it is crashing because xaml resources couldn't be find.
Any idea?
Thank you very much.
P.S. It seem that XAML resources aren't really included in Resources in the assembly. If assemble is just rebuilded (without Publish) everything is ok and XAML are included in resources.
Have a look at the One Click Deployment options on your project.
On the Publish tab, have a look at the Application Files section.
Some files might not have been included.
It seems I solved this problem.
My application has been upgraded from V2k5 to V2k8.
If .NET 3.0 is target platform, the problem exists.
If .NET 3.5 is target platform, problem solved.
Thank you for your collaboration.