Sharing styles between modules in Silverlight applications based on Prism 4 - silverlight-4.0

I need to use the styles in several modules in Silverlight application based on Prism 4.
What is the best approach for this?

You can achieve this by adding the resources to your prism shell project and adding a reference to the shell module project in all the other modules.

Related

How do I know if an application uses Silverlight?

I am looking at a legacy .NET application and need to know if it is using Silverlight. If it is, I need to migrate the code to WPF, XAML, or HTML5.
Is there a specific set of namespaces and references that tell me that this is a Silverlight application?
Some indicators:
the ProjectTypeGuids element in the .csproj/.vbproj files contains the Silverlight project GUID: {A1591282-1198-4647-A2B1-27E5FF5F6F3B}
the System.* dependencies, when observed in the property grid in Visual Studio, would have version 5.0.5.0 or similar.
You can see a Silverlight project property with bellow link
Silverlight project property

How do I import VisualBasic.MyServices in a Console Application?

I am creating a Console Application in Visual Basic. I would like to use features like My.Computer.FileSystem like I would in Windows Forms but it is unreferenced in my project.
After a bit of googling, I came across this namespace called Microsoft.VisualBasic.MyServices which appears to contain things like FileSystem which I am unable to access with my Console Application
I have tried referencing a few different libraries that I found in COM Components, but none appear to include MyServices
I know this is possible because I used to be able to do this when I worked with Console Applications a few years ago.
Any help would be appreciated.
Thanks.
I have tested to confirm and, using VS 2019, the My namespace is supported as usual in a VB Console Application project targeting .NET Framework 4.8 but it is not supported in a similar project targeting .NET Core 3.1. I'm not sure what the situation will be in .NET 5 but, for now, stick with .NET Framework or forgo the My namespace.

Xamarin Forms code sharing

I'm working on a xamarin forms (PCL) project (A basic customer care chat app which is meant to run on Android and iOS only) that has just two xaml pages, custom renderers and few dependencies. This project is meant to be implemented into another existing project (which I don't have access to its source code) such that an action would be binded to a button on the existing app to show a page on my own project.
There is need for me to share my chat project with my client's developer but without exposing my source codes, perhaps compiling to dll or nuget package that would be added to the existing project to access my project's functions and pages. I have searched through the xamarin forum and here on stackoverflow but can't seem to lay my hands on a solution.
Is this possible at all? If yes, what am I missing? If no, is there any better option to use?
Please do note that the chat app completely done, so I'm hoping perhaps there's a way I could directly convert the project to a Nuget package.
Thanks in anticipation!
If the host application is a Xamarin Forms one:
-Move your cross platform shared code into a PCL or .Net Standard (ContentPages, ContentViews, Classes).
-Move your Renderers and platform specific code to Android and iOs Class Libraries.
Your client will have to reference your first assembly (dll) in their XF assembly in order to instantiate/manipulate your views/classes and platform specifics one on their Back-end side (taking into account your renderers, effects, etc ...)
A lot of Xamarin Controls Libraries Open Source hosted on Github are working like that. For example this one: https://github.com/jamesmontemagno/Xamarin.Forms-PullToRefreshLayout
If the host application is a native application, take a look into Xamarin forms embedding
Finally, I seem to solve the problem by enabling visual studio to build Nuget packages for the chat app project (summing up to 3 nuget packages) on project build.
Thanks #Rudy Spano and #Micah Switzer for your contributions

WinRT MVVM Light Sample Project

If anyone starts developing Windows 8 metro applications using MVVM Light please help me to create a Windows 8 (WinRT) project template. I get bored by using Microsoft ‘s Layoutaware page(Base class). I just need to structure the class with the help of MVVM Light. If any one did this please help me or provide some links to start developing Windows 8 Metro application using MVVM Light.
The major areas where i am facing issues are:
Navigation (Forward and Backward)
State Handling (Tombstoning in windows 8)
Navigation after the app launches form termination state etc.
Handling WebService [ Post using http client ]
There is an (older) example of using MVVM Light with windows 8 found here. There are also templates and Samples as part of the MVVM Light source found here.
Edit:
Here is an msdn example using MVVM Light.
What about this
But I did not try it. I'm using Portable class library (with targets Windows 8.1 and .NET x.xx) and this library is referenced to WinRT project. MvvmLight for PCL you can find on this link
Problem is, that you can't access Local files and Local settings but you can inject it from Presentation project to Portable class library at the start.
This solution has a lot of advantages and one of the is : easiest unit testing.
For more info look this stack overflow thread

How can I get Ninject to work in WIndows 8 metro style app

Has anyone managed to get Ninject working in Metro Style app using the Windows 8 Developer preview?
If so how?
Running Ninject in Metro Style apps requires several changes in the implementation of Ninject. Therefore there is no way to run current builds in metro style apps. If you are willing to do the required chages to Ninject then you have to perform the following steps
Create a new MS library project
Add all files from Ninject
Define NO_LCG NO_ASSEMBLY_SCANNING NO_EXCEPTION_SERIALIZATION
Fix all the problems related to the chages to the new reflection API
Otherwise you have to wait until there is an official preview of Ninject for Metro Style Apps which will be available sometime after the Ninject 3.0 release.