Can I develop for MonoTouch using VB.NET? - vb.net

Is there any way to develop for MonoTouch using VB.NET, rather than C#?

Currently Visual Basic is not supported in MonoTouch, but we plan on adding this to the mix in the future, as well as expanding our language support.
The reason for our lack of support is that in addition to shipping the VB compiler, we have to ship templates and we have to port the VB runtime which currently has many dependencies on desktop features of .NET and Mono.

Currently, C# is the only supported language in Monotouch. Also, Monotouch apps are not your average managed .net assemblies. Monotouch C# code is compiled to native code (similar to Vala)
I don't expect to see VB.Net in Monotouch in the near future - as of now, Miguel and his gang is busy with Monodroid & the Mono framework proper. According to their roadmap, they do have plans to support VB.net in the future. No time-frame has been mentioned.

Related

Using Mono to complete Universal Windows Platform (.net core)

We are using some old open-source .Net Framework libraries that depend on things that are not in .Net Core. Can Mono be used to fill in the rest of .Net Framework?
Specifically I'm thinking of creating a Universal Windows class library that includes everything in Mono (excluding some of the System namespace) that changes the namespaces from System.* to MonoSupport.System.*.
Of course, better approaches would be to re-write the library's code, use a different library, or be more selective in taking things from Mono. I was hoping to do this as a temporary measure.
(I want to use iTextSharpLGPL but it uses XmlTextReader, streams with .Close(), System.Security.Cryptography, etc.. The pay version of the library does not support UWP either.)
Edit: I gave up on this and rewrote my app to use Apitron. That worked great until I tried to deploy and found out they don't support .NET Native. I'm now waiting for some library to support PDF generation on UWP.
I do not think so. The following immediate reasons
Mono is a clone of the .NET Framework and therefore based on mscorlib ideas, while UWP is based on System.Runtime. Would require significant extra effort.
UWP apps - when released - are based on the .NET Native runtime. This runtime enforces some patterns in the library implementations (e.g. no reflection, no C++ implementation of types etc). Mono is also strong in AOT, but I think there are dragons.
Mono is a bad choice. Better is the microsoft referencesource for the .NET Framework as published on github.
The time you will invest in your plan will be so significant high, it is much better invested fixing it in corefx directly and wait for the next release of UWP to contain your fixes.
For your problem I would urgently recommend you to fix the problem as a submission upstream at iTextSharpLGPL by surfacing new methods and removing of close or maybe by just copying the MIT licensed XmlTtextReader. But I highly recommend you, not to mess around with crypto ;)

Sharpdevelop using Mono

Is it possible to run sharp develop on Linux using mono?
I have already tried it on wine but the only supported version is 2.n
This version does not support .Net 4.*
No, it is not. MonoDevelop is a fork from SharpDevelop precisely because at the time SharpDevelop could not run on Mono, and that has not signifcantly changed since then. In a way, this situation shows the flaw in Xamarin’s strategy of following MS .Net, which is a moving target. But MonoDevelop is useful for whatever is portable in .Net, which excludes MS VB.Net & WPF.

Compile my VB.NET application for Mac and Linux

I have just finished my vb.net application and I wanted to compile it with Mac and Linux as well.
I have looked around and found mono project... I tried to use mono to open my application but the GUI is not as it should be. so my question is: there is way to maintain my Gui even on other platform? If not there is an IDE for Mac/Linux that support vb.net? I use Xcode for programming in c but the GUI Builder is so hard to use... There are other simple IDE/Gui Builders?
Of course it will be great if I can build directly from visual studio or with some simple way as well.
Thanks for all future replies.
Mono's VB.NET was not very mature. So you might hit both compiler and runtime issues.
If possible, evaluate and wait for .NET Core.

Does Xamarin support COM?

Does the MonoProject or Xamarin studio support Microsoft's COM technology? Was wondering if I could use the ole32.dll in mono. I can already use some dll's for .net, but I get a not found exception when using others that rely on ole32.dll.
No.
Mono 1.0 and Mono 1.1.xx do not have support for COM, it is a known
missing feature of Mono. Initial work has begun on supporting MS COM
on Windows. The long term goal is to support a variety of unmanaged
component technologies including MS COM, XPCOM, and UNO.

Are Metro style apps managed or native and if native how can they run on both arm and x86?

I originally assumed that Metro style apps were managed (.NET) assemblies whether they are written in C# or C++ and I thought C++ for Metro style apps would be similar in concept to C++/CLI.
However, I now heard on a DotNet Rocks podcast that Metro style apps written in C++ are native. Nevertheless I understand that Metro style apps run on all three CPU architectures Metro is available for. How is this accomplished? Do Metro style apps come with different binaries and only one is chosen/downloaded? Or is it like on Mac OS X where one binary can contain code for different CPUs?
Code that uses only system or OS services from WinRT can be used
within an app and distributed through the Windows Store for both WOA
and x86/64.
from this MSDN blog page
If you go watch this BUILD video things should start to clear up -- http://channel9.msdn.com/events/BUILD/BUILD2011/TOOL-930C (A .NET developer's view of Windows 8 app development)
Basically there is a CLR (.NET 4.5) running. I didn't say a full CLR. WinRT from a .NET perspective is just a .NET Profile (sort of a way that they can layout the API differently exposing or hiding things). The new WinRT APIs use a new version of [gulp] COM, but it is optimized for use with .NET. I'm not 100% sure on the C++ angle. I suspect with C++, you have a few options. Compile for each platform (arm and x86) or compile to IL. Not sure if this helps you at all (I hope so).