Jump to content
Sign in to follow this  
ozmike

Windows 10 - Project (C)entennial apps will it work for auto IT?

Recommended Posts

Hey could be interesting to the AutoIt devs out there 

Will win32  apps (autoit apps)  work in the new windows 10 store? 

Early days yet won't be in the initial win 10 release...

 

Note  win32 apps are now called many things

- desktop apps

- CWA ( Classic Windows Apps - not country womens ..assoc. ) 

- Project C(entenial) apps 

These apps will not be sandboxed but NOT be allowed to run as admin , all files will be sandboxed installation handled through the store..

 

blog link

How does this affect autoit - ?

FYI

 following as not supported in Project C apps:

  • “Windows NT Services”,
  • “Things running in the kernel” (device drivers)
  • “System Level Software” (anything not running in the user context)
  • “Elevation”, meaning anything that causes a standard user to get a UAC prompt “will be blocked”.

Using parts of other apps in your app, at least in version 1. John indicated that they would like to support extensibility and plug-ins, just probably not initially. The implication was that this might be a direct UWA thing and not specific to Project C, but we can’t be sure.

 following as supported in Project C apps:

  • “COM”
  • “WMI”
  • “Networking”
  • “Anything else a standard app does that isn’t in the system space”.

I am guessing that there are a lot of other things that might end up in the ‘not supported’ list that you might have thought falls under the last item in the supported list but turns out is not supported, but we just don’t know yet:

  • WMI Providers
  • Windows Timed and Triggered Events (but they can write new UWA background triggers)
  • Custom ETW Providers
  • COM localsystem (out of process) running as the system to avoid UAC prompts
  • Maybe DCOM
  • Software Clients,
  • Application Capabilities
  • Shell Extensions, Browser Helper Objects, and the like

 

FYI

Share this post


Link to post
Share on other sites

Provided the programs created with AutoIt fall within the set outlined bounds then I can see no reason why they would not.

But it sounds to me like, once again microsoft are trying to push their vision on everyone else.

EDIT: after reading the blog link you posted, I take that back, first it says it converts applications, then later it says it is targeted at developers who have access to source code, so if it converts apps, why do you need access to source code? 

Probably because there will be some sort of SDK for visual studio or something which you have to use, ot this converter scans the code in some fashion and indicates changes that need to be made, so it's actually doubtful, although it did hint that simple apps could be converted without access to source code, but those apps would not make it to the windows store.

So I suppose it's up in the air.

Edited by JohnOne

Share this post


Link to post
Share on other sites

My guess - You will need the source code - because you will have to make changes to get it to work in the windows store!

most win 32 app will work on windows 10 - but to submit apps (exes?) to windows 10 store will need a recompile?.

Any exes out there already - can't submit to the store as is probably .. whether an auto it script needs to be compiled inside Visual Studio or  an exe can be submitted we will  have to wait an see.

I bet microsoft don't know yet .. early days..

 

MS plan to allow android and iphone apps in window 10 ..so its early days.!

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Similar Content

    • By gahhon
      I have a application that have a function is to create a shortcut to desktop, lets say is ChromePortable.lnk.
      $iCreate = FileCreateShortcut($DIR_WA_FOLDER & '\GoogleChromePortable.exe', $DIR_SHORTCUT, $DIR_WA_FOLDER, '--kiosk "https://example.com/"') So the shortcut will be launch as kiosk mode and force to enter the specific website. However, the user is still able to right-click on the shortcut and modify the target value to remove the kiosk mode. What can I do to disable the user to editing the target value?
      So far, I had asked and tried from SuperUser for advises Disable Shortcut Target Field
      icacls "ChromePortable.lnk" /GRANT EVERYONE:RX So this will set the permission of this shortcut file to only Read & Execute only! But after I set it, the user is still can modify.
      Please kindly advise.
      Please note and assume that user don't have Administration account or etc, that should be only have 1 account to logon to the computer.
       
      EDIT:
      I must disable inheritance to remove all others permissions like SYSTEM, ADMINISTRATORS, etc. Then only GRANT everyone for READ & EXECUTE only.
      But still the user can go to edit the permissions tho. Any advise?
    • By morion84
      Hi, when I call a MsgBox function I can use a "$MB_SERVICE_NOTIFICATION" flag so it will be displayed "on the current active desktop, even if there is no user logged on to the computer.". That works just great. Is there a way to do the same to Autoit GUI Form so it will be visible on desktop even if running from system account and user is not logged?
    • By ur
      When I compiled my script or any script to exe using 32 bit compiler and ran on 32 bit machine, I am getting below error.
       

       
      But it is 32 bit only.
       
      And, for testing, I disabled smart screen also, but same issue.
      Please suggest.
       
    • By sadakathullah
      Hi All, I am new to AutoIT and exploring options to use it in my organization. I tried couple of examples and it is fantastic. I am trying to run restrictions test in a pc to see if certain options are disabled like print screen, mstsc etc. I could not get a hang of it. Any help is much appreciated.
    • By stayready40
      Hello all. I created a script to uninstall Symantec from our environment and I placed the "BlockInput(1)" command in the beginning of the script so that end users would not be able to move the mouse or keyboard to disrupt the mouse clicks.
      During testing we found that this worked for our Windows 7 machines, but for our windows 10 machines the mouse disable did not work can anyone shed some light on why this is? 
      Here is my code:

       
×
×
  • Create New...