We Keep Coding

Can we set themes in GTK 3 for Windows?

In Ubuntu, installing themes are as easy as copy-pasting GTK theme into the themes folder, then with the tweaks tool we can select the theme.
I couldn't find a working solution or workaround to apply themes.
Steps I have tried:
Installing the runtime
The GTK runtime I am using is
https://github.com/tschoonj/GTK-for-Windows-Runtime-Environment-Installer/releases.
Get a theme from https://www.pling.com/p/1246387/
Extract the content to C:\Users\username\AppData\Local\Gtk\3.24.24\share\themes
Edit settings.ini on C:\Users\Seiko Santana\AppData\Local\Gtk\3.24.24\etc\gtk-3.0\settings.ini putting gtk-theme-name=Ultimate-Dark-(Cpt)-Violet
Run any GtkSharp application.
It is still loading Adwaita theme. Did I miss something? I'm developing on .NET 6 and GtkSharp if that matters.
Thanks in advance.

I put the theme file under the themes directory like so:
, and added the following code right after Init (if I put it before that, it causes a null exception).
public static void Main(string[] args)
{
Application.Init();
Gtk.Settings.Default.ThemeName = "Ultimate-Dark-(Flat)-Violet";
and it worked:
Without that line, the default theme is like this, so it definitely worked.

C# intellisense not working in VS Code

I am using Visual Studio Code and I have already loaded C# OMNISharp plugin to my system and it works all fine in my existing project/solutions.
However, I just created a new solution and a new project in Visual Studio code and it sounds like for this particular solution, the Intellisense or any other Omnisharp features are just not working. I have tried following things:
Restarting Visual Studio Code
Disabling and enabling my OmniSharp Plug-in
Also, one thing that I noticed is that when a solution is created in Visual studio, it has a lot of code which looks like following:
Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "src", "src", "{AEA16303-6991-4FF1-A3A9-72D892D7968C}"
EndProject
Basically, these are all project references. However, when a solution is created by Visual Studio Code then there is not any section like that. This solution runs and compiles fine, just that it looks fundamentally different than how a Visual Studio solution looks like.
However, nothing seems to be working. Is there anything that I can try to make it work? Any ideas ?

It's caused by adding *.sln and *.csproj to your "files.exclude" setting.
Try this:
Code -> Preferences -> Settings -> "omnisharp.useMono": true/false
Remove from setting file.
Or, Open your project with MonoDevelop or Visual Studio 2015/2017 first, then reopen VS-Code.
Edit 1: Try setting "omnisharp.useGlobalMono": never and then restarting the omnisharp server.
Credit: The_Wolf and kao peter

How did you created the project?
For the Intellisense to work properly the project needs to have a specific structure.
Assuming you have the .net core sdk for mac and the omnisharp extension installed:
Try the following:
Open your integrated terminal (View => Integrated terminal)
Create some new directory to host a test project say "testproj" e.g => mkdir testproj
use the dotnet cli to initialize the project => dotnet new console
See if you got intellisense.
Also i'd recommend watching the .net core on Mac introduction video.

In VS Code v1.43.2 adding following line to settings worked for me:
"omnisharp.useGlobalMono": "never"
The setting's value "never" had to be double-quoted otherwise it would be flagged in red. Even with the quotes, it remained highlighted in yellow. Not sure why, as all other options/values in there are blue. I presume this indicates some sort of warning, but it works.
(As an aside, I would love to understand what a "Globally installed mono" is. However my only interest here was getting IntelliSense working, so re: omnisharp I'm pleading 'newb'.)

This worked for me
"omnisharp.useGlobalMono": "never"

Were your new solution and projects created in a "OneDrive" folder in Windows 10? In latest Windows 10 release, the C# plugin can't start up when a project resides in a OneDrive folder with "File On-Demand" feature on. Please take a look at this issue on Github

I my case, the problem came from the resource folder of my project.
I had added a visual studio .sln file in the ressources to be used as a template but I somehow "variabilized" it with custom tags. OmniSharp tried to parse it and obviously failed, but no error poped up in VSCode, it was only visible in OmniSharp output.
The solution was to rename the template from .sln to .txt to prevent OmniSharp from loading it.

In my case, after installing C# extension, I had to click the setting icon on the extension and then click "Add to workspace recormendations"

I had this problem in 2022 and nothing mentioned above worked for me.
For me the problem was caused by VS Code and C# plugin being updated (in my case c# plugin to v1.25.0+) because in this version they made this:
.NET Framework builds of OmniSharp no longer ship with Mono or the MSBuild tooling (See announcement omnisharp-roslyn#2339). To ensure that the C# > > extension remains usable out of the box for .NET SDK projects, we have > changed the default value of omnisharp.useModernNet to true.
If you still need Unity or .NET Framework support, you can set > omnisharp.useModernNet to false in your VS Code settings and restart OmniSharp.
So entier problem was in omnisharp.useModernNet being set to true by default which renders entire plugin unfunctional but doing what they said and setting
omnisharp.useModernNet to false manually in .vscode > settings.json file solved this problem for me!
For more info, you can also read the entire official VS Code C# Plugin announcement under plugins Details section in VS Code or on this webpage as well!

Android app debugs for a few seconds then just stops

I'm trying to set up a new Android app development environment at home and I've run into a problem that is a showstopper.
First, here is my environment:
Windows 10
Visual Studio Community 2015 with Xamarin platform installed
Test device is: G Pad 7.0 LTE
Android Version 5.0.2
I'm following this tutorial: MSDN tutorial
When I go to debug my test app, here is what happens.
Select debug from Visual Studio with my tablet as the target
VS deploys to the tablet
App starts on the tablet
App and debug session runs for about 5-10 seconds.
Debug session ends and app closes
No errors are displayed in Visual Studio and when i turn on Android logging it's a such a massive overflow of information that I don't really know where to begin searching for a problem.
Please also note that when I first set up the app, according to the tutorial, debugging on the tablet worked fine. The initial build is simply a template with a few basic controls.
In between then and when it stopped working I also added and successfully tested a Windows Phone project on a Windows Phone device.
Once I got to the section where I was modifying the project is when the problem started. I thought that perhaps a change in the code I did caused this issue so I tried another blank app and that blank app now crashes as well.
When I deploy the tutorial app to an emulator it crashes immediately but when I deploy a blank app it doesn't crash.
I also tried restoring the tablet to factory defaults and testing again. Same scenario: Blank app and tutorial app run for a few seconds, debugging stops, app closes.
Any clue as to what type of problem I'm looking at?

Solution
Clean your project (Right-Click on Project and select clean)
Go to your build folder. Probably in your Android project's root folder, named "obj". Delete either build you had, when you ran into this behavior (Debug or Release).
Directory Path
./AndroidProject/obj/Debug
./AndroidProject/obj/Release
Restart Visual Studio
Build and run again and it should work just fine, as the md5-hashes are now matching again.
I had also uninstalled the app before from the device and restarted it, I don't know whether this is required anymore, because the app is now being "reinstalled" by newer Xamarin versions anyway.
adb uninstall com.your.domain
Story and Background information
Have had the same issue with a device running Android 5.0.
Basically, the app was just stopping without any note.
When I now restarted the phone, The log was extended (once) by the following line:
Device could not find component named: *com.your.domain*/{*md5hash*}.*{Activity}
It turns out that with Andrpod 5.0 a hashing mechanism was implemented:
With the 5.0 release, the default package names for Android Callable
Wrappers will be based on the MD5SUM of the assembly-qualified name of
the type being exported. This allows the same fully-qualified name to
be provided from two different assemblies and not get a packaging
error.
See this for further information Xamarin.Android 5.1
So, if the md5-hash now changes from time to time, a simple Clean of your project is not enough.

I ran into this same issue and applied the same solution described above many times, which seemed to remedy this particular problem.
A possibly related fix, but definitely worthwhile note
After releasing this Android app and later releasing updates to the app, we got feedback from users that their Android Home screen shortcut to the app was disappearing after each app update. This is not good, for obvious reasons, but the fix for it was very simple as noted here:
dream-team-mobile-blog - Android app removes shortcut on update Xamarin solution
On the main activity, set a Name attribute of
<your package>.<your main activity>
like:
com.mycompany.myapp.MainActivity
For my solution, I chose to do it in code like this:
[Activity(Name = Constants.PackageName + "." + nameof(MainActivity),
Label = Constants.AppIconTitle, Icon = "#drawable/icon",
Theme = "#style/splashscreen", MainLauncher = true,
LaunchMode = LaunchMode.SingleInstance,
ConfigurationChanges = ConfigChanges.ScreenSize | ConfigChanges.Orientation)]
//Side Note: I change my PackageName between Prod and SQA builds, so using
//a constant as seen above makes that change less risky to miss maintaining.
//Also, using nameof() keeps things tight and a sure match.
public class MainActivity : global::Xamarin.Forms.Platform.Android.FormsAppCompatActivity
I mention it here in this post because, having this fix in place may have:
definitely prevented app shortcut loss and
possibly prevented the issue discussed in this post
as the MD5 hash prefix from the Main activity seems to no longer be generated.
This tweak may fix two bugs with one fix. If not, implementing a fixed main Activity Name will surely help your users keep their shortcut to your app when you release updates!

What fixed it for me in Visual Studio 2017 is going to :
Tools → Options → Xamarin → Android Settings
and uncheck:
Preserve Application data cache on device between deploys

go to your AndroidManifest.xml and change your package name.

UWP initializeCompontent Error

I changed all the namespaces in my app. It was a grueling process. but now my app won't build because of this error. See the attached screenshot.
Can anyone help me fix this issue?

You must have missed something. I just tried this on a new solution, and it worked fine, using Visual Studio 2015, Update 1.
Create new UWP app (ILoveBurritos)
Rename namespace using F2 to ILoveTacos
Resulting app still compiles and runs

Windows 8.1 Bing map control

I have added the bing map reference and name space but when I drag and drop the map control to my designer it give me an error.
A reference to "Bing.Maps.Xaml, Version=1.313.0825.0" has been added to the project.In Order to use types from the new reference,Press ok to restart the XAML Designer. After
the XAML Designer restarts, Re-create the control on the artboard.
I have restarted the xaml designer and tried new project but all in vein.

in vs2013, Select BUILD from the main menu, then Configuration Manager.
Choose x86 its done

Create an app with Bing Maps (for Windows 8.1) read msdn.

I think you can download http://code.msdn.microsoft.com/windowsapps/Windows-8-Modern-Style-App-Samples samples (it contains 200 samples for "Windows 8.1").
And you can have a look what BingMap app sample does thing different than your app (and also maybe you can try to add sample's dll to your application, there could be a version difference.)