|
RyanDev wrote: I started learning before the internet and had to do a lot more work to learn. There is value in that.
I think that there is huge value in doing your own research. finding the books, and actually reading them is irreplaceable, that's the reason I do not answer such 'question' like it was valid... not because this is The Lounge, but because it is me...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Kornfeld Eliyahu Peter wrote: before coming here to ask a questions
Oh, is it a big waste of your time to read his question? What are you, some bearded guru on top of a mountain?
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
Richard Andrew x64 wrote: some bearded naked guru on top bottom of a mountain lake
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
32bit .NET exes look pretty simple, they have an entry point that does
jmp [0x402000]
Which is where _CorExeMain is imported from mscoree.dll, so that's probably what "does the .NET thing".
I couldn't quickly figure out 64bit .NET exes, their entry point is 0 but that would execute the MZ header.. some other magic is going on there.
|
|
|
|
|
It is true that you! can figure out from the EXE from which language it was compiled and even on what compiler and OS, but all that irrelevant to the OS, running your EXE... It cares no, just load and run it... If it has a JMP at the beginning or a NOP it is up to them...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Well that was my point, the OS doesn't have to figure out anything, a 32bit .NET program starts as a native program which itself, by taking that jump, starts up the .NET stuff.
modified 8-May-17 8:51am.
|
|
|
|
|
It is a Q&A question.
Answer: Files have an extension which is a hint how the OS how to interpret some header information in the file.
Press F1 for help or google it.
Greetings from Germany
|
|
|
|
|
I don't know about iOS, but Microsoft and Google have mutual-support data-sharing agreements with the NSA,so they just look it up in a database.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Hmm...
That message took a ridiculously long time to post.
It must be tea-break at the n-s-a HQ.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
|
I thought for one moment you were going to link to last weeks Oglaf with the same subject - which was (as usual) NSW ...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
OriginalGriff wrote: Oglaf
What's an OGLAF?
OGLy As F*ck?
I only have a signature in order to let @DalekDave follow my posts.
|
|
|
|
|
It's a cartoon strip. But ... do not, at work, search for it: it is frequently VVNSFWAT1 and should probably not be read by anyone without a mind broad enough to be tied in a bow under your chin.
Can be very funny - but is nearly always very rude.
1: very, very NSFW at all
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
OriginalGriff wrote: it is frequently VVNSFWAT1 and should probably not be read by anyone without a mind broad enough to be tied in a bow under your chin.
Sounds like my kind of humor.
I only have a signature in order to let @DalekDave follow my posts.
|
|
|
|
|
Just add ".com" to the end.
This weeks is pretty tame...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Just installed Visual Studio 2017 in an effort to examine Xamarin for building apps for deployment everywhere.
1. First thing i notice is that *I can choose a Xamarin app for Android OR iOS? That is confusing to me. I just want to build a Xamarin app that runs everywhere, right?
*EDIT -- Figured this out -- Didn't see this type of project before - it's called Cross-Platform and it's under another section on the Project Template area.
2. Next thing that happens is that Visual Studio 2017 gives me an error when it attempts to run my first app from the Xamarin.Android template. The app builds fine, but it won't start the emulator. VS 2017 failed to add a environment variable ANDROID_SDK_ROOT -- I've documented the problem at:
xamarin - Why won't Visual Studio 2017 run Android emulator? (Gives error ANDROID_SDK_ROOT missing) - Stack Overflow[^]
3. After fixing that, I add two simple controls (Button and EditText) and try to run again. Now the controls will not show up in the app, even though they render properly in the VS 2017 design window.
I've posted a question at:
android layout - In visual studio 2017, why won't xamarin app controls (button, editText) show up? - Stack Overflow[^]
This is the state of EASY DEVELOPMENT and
Quote: Build Once Run Everywhere
So far, I'm meh about the whole thing.
It's much easier for me to use Android Studio.
yes, I happen to be looking for miracles.
I would like to build some apps at lightning speed. It's all a dream though.
modified 7-May-17 19:08pm.
|
|
|
|
|
I've been using Xamarin.Android to build Android apps using VStudio2015/C# with great success. I don't use an emulator, but debug on a physical device (Google Nexus). I find this to be convenient and fast. Haven't yet moved to VS2017.
/ravi
|
|
|
|
|
Ravi Bhavnani wrote: I don't use an emulator, but debug on a physical device (Google Nexus).
That's probably the best option really.
Lately, I've also ran Android Studio from a VM and then I use Genymotion [^] Amazon Web Service which runs android emulators in your browser. YOu just drag/drop your APK on the emulator running in the browser window and it works quite well and amazingly fast.
It was kind of a pain to set up though, but interesting.
|
|
|
|
|
I found that Xamarin was occasionally a pain to install and/or configure.
And VS2017 continue the tradition with a disappointing install experience.
However, once you get it going, it's all good!
My biggest gripe with Xamarin on VS2017 is that it does NOT come with VS Android Emulator.
And one has to go through some hoops to use it...
|
|
|
|
|
Super Lloyd wrote: However, once you get it going, it's all good!
That's good to hear.
I guess I had issues with AndroidStudio in the beginning too.
I was also fortunate because running the Android emulator is always a pain and I am happy to say that VStudio 2017 seems to find the Android SDK and use the same emulator and images so no double-install.
|
|
|
|
|
raddevus wrote:
I would like to build some apps at lightning speed. It's all a dream though. Is your lightning cable installed?
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"You can easily judge the character of a man by how he treats those who can do nothing for him." - James D. Miles
|
|
|
|
|
|
Interesting. I'm going through the same pain and am actually thinking of just switching to native app development. It seems like a whole lot of loops to jump through that, frankly, shouldn't be there.
cheers
Chris Maunder
|
|
|
|
|
I find this surprising. I've been doing Xamarin development for a while now and don't see any of these issues. The problem most people have is that they rely on the native Android emulator; this is a slow beast and you're much better off using the x86 emulator.
This space for rent
|
|
|
|
|
It wasn't the emulator that was an issue (and to be honest I didn't see a huge difference between the Android one in 2015 and the MS one in 2017 - though I barely used them).
The main issue was that things simply didn't build. I would fire up VS 2015, create a new project from their templates, and they would not even compile.
I had some other issues[^] with iOS, and the Android part seemed a long series of installing 50 SDKs all named the same without any real guidance on what was actually needed. 40Gb later and that seemed to sort itself out.
I do not have my head wrapped around Xamarin forms even vaguely at this point, and the demo apps I've tried (mainly involving bluetooth) just don't work.
My wild guesses as to the issues
- Android moves quickly and keeping up with requirements makes life hard for Xamarin, hence the shotgun approach.
- Xamarin tries to use what the other vendors provide meaning they can't provide a neat, integrated "we'll set this all up for you" experience
- Dealing with XCode is just going to be painful. I'm sure that's not by mistake
- The native iOS/Android community has way more mature and stable examples than the Xamarin community. It's just the nature of the beast
So I'm heading to native so that
a) I can just get started
b) I can lean on lots of existing code samples
c) I can understand what's actually happening before I abstract it all using Xamarin
cheers
Chris Maunder
|
|
|
|