• Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
  • Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
Collapse

You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:

  • You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
  • You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
  • If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.

Previously on "Picking up coding again"

Collapse

  • TheGreenBastard
    replied
    Originally posted by woohoo View Post
    If his application is for the mac desktop rather than iphone etc does he have to sell it via the app store?
    See below, yes it's not a prerequisite on Mac to release via the app store (as much as crApple would like that) - but it does have advantages for startups: exposure.

    Originally posted by meanttobeworking View Post
    My definition of production is release to the App Store.

    Leave a comment:


  • woohoo
    replied
    Originally posted by TheGreenBastard View Post
    App store has sandboxing rules so it might be wiser to trial implementing in Swift; you'll also get 100% Apple SDK coverage.

    My worry with .Net would be how Apple views the runtime; they have strict anti-runtime / code execution policies that will be caught during app review.
    If his application is for the mac desktop rather than iphone etc does he have to sell it via the app store?

    Leave a comment:


  • TheGreenBastard
    replied
    App store has sandboxing rules so it might be wiser to trial implementing in Swift; you'll also get 100% Apple SDK coverage.

    My worry with .Net would be how Apple views the runtime; they have strict anti-runtime / code execution policies that will be caught during app review.

    Leave a comment:


  • Platypus
    replied
    Originally posted by meanttobeworking View Post
    Thanks Platypus and Snarf for the advice, really appreciated!
    YW.

    I'm also 'picking up coding again' after years of honing my Powerpoint skills, now I'm doing something productive, and it feels good!

    Leave a comment:


  • meanttobeworking
    replied
    Thanks Platypus and Snarf for the advice, really appreciated!

    Leave a comment:


  • Snarf
    replied
    Originally posted by meanttobeworking View Post
    Hi all,

    I have a history of coding HTML/CSS/JS/SQL/ASP/C# but stopped round about .net 2.0, so quite some time ago.

    I’ve got an idea for a Plan B project, and I’d like to knock up something of a proof of concept, ideally running on OSX. It’s not a tremendously complex concept but will require detecting when various devices are connected / disconnected via USB.

    Does anyone have any pointers for how to start? I’m not looking to produce any code that goes into production.

    Thanks!
    If you're familiar with C# then I'd suggest .Net core - it runs on windows, OSX and Linux.
    You could also look at full fat .Net but to run on anything other than windows will require mono and I didnt have much luck with it when I tried it years ago!

    Leave a comment:


  • Platypus
    replied
    Use Xcode on the Mac - it's pretty amazing

    EDIT: See also https://stackoverflow.com/questions/...evice-is-conne
    Last edited by Platypus; 11 May 2018, 12:06.

    Leave a comment:


  • NigelJK
    replied
    UWP xplatform and os agnostic from VS

    Leave a comment:


  • uncle pear
    replied
    Visual studio community edition is free, so I'd start by downloading that. That should be plenty for you to get your PoC off the ground.

    Leave a comment:


  • woohoo
    replied
    Originally posted by meanttobeworking View Post
    If it takes off it’ll be cross-platform, I wanted to write the proof of concept app on a Mac because I have a Mac
    Hah I asked a stupid question sorry, makes sense now.
    Good luck with the prototype!

    Leave a comment:


  • meanttobeworking
    replied
    Originally posted by woohoo View Post
    Out of interest why is this plan only for the Mac?
    If it takes off it’ll be cross-platform, I wanted to write the proof of concept app on a Mac because I have a Mac

    Leave a comment:


  • woohoo
    replied
    Out of interest why is this plan only for the Mac?

    Leave a comment:


  • meanttobeworking
    replied
    Originally posted by woohoo View Post
    You can run .net core on OS X and use Visual studio. So you could at least leverage your c#.

    I’ve never tried it though so take it for what’s its worth.
    Yeah I saw that was an option, thanks. I wonder how much of it I’d remember

    Leave a comment:


  • meanttobeworking
    replied
    Originally posted by Lance View Post
    If it’s not for production use WTF is it for?
    Or do you have a different definition of production?
    My definition of production is release to the App Store. I want to build a proof of concept cheaply, so I can get a feel for what’s possible without having to code for too many edge cases etc, and then if that goes well, get the app properly developed by someone that actually knows what they are doing.

    I know there are other ways of prototyping, but I’m seeing it as a bit of a learning exercise for me too.

    Leave a comment:


  • woohoo
    replied
    You can run .net core on OS X and use Visual studio. So you could at least leverage your c#.

    I’ve never tried it though so take it for what’s its worth.

    Leave a comment:

Working...
X