I have some Windows Mobile Smart Device applications coded in Visual Studio C# that use FTP for the send/receive mechanism. It's not ideal, but it works.
I've been investigating whether these can be ported over to Windows Phone 7 and the major problem is the lack of FTP in Windows Phone. With 7.5/7.1/Mango I'm interested whether Sockets can be used but I can't find a decent wrapper out there. I've started work on my own but I was wondering if I'm just replicating work already available.
Our SecureBlackbox component suite includes FTP/FTPS and SFTP client components for Mango.
Related
Thinking more about leaving my MBP at home and instead taking the new Samsung Chromebook PRO to Starbucks for the day.
Is this fantasy or will VS Code run properly on this new machine? I see options for the Arm chip based PLUS model but nothing for the PRO.
Is a port available and if so how has development been, good?
UPDATE
I guess this is a hard question to answer? Essentially, I just want to leave my heavy MBP that always needs a power outlet at home. Just want to head out with a light weight machine and work on it anywhere.
The PRO does run Linux but I have not verified clearly that VS Code can run in this environment. Being in Canada I have no access to the PRO yet, can only order it from USA at this point, which I might do once I know the verdict to my question.
My team and I have been experimenting heavily with the Samsung Chromebook Pro and have been actively switching our development environments completely over to the Chromebook ecosystem (away from Mac). Personally I run a combination of Atom and NeoVim with a complete development environment for Node.js, Postgres, and Redis on my Chromebook Pro.
For any desktop IDE you'll need to run Crouton which means you'll have to put your Chromebook into developer mode which is less secure. If you don't want to do that your only options are either use something like Caret (which will only do basic text editing) or to use some sort of cloud-based IDE; ones I know of: Cloud9, Codenvy, Shiftedit, and Eclipse Che (an open source one that just recently caught my eye).
The good news is Crouton can run effectively anything that Linux can (especially since the Pro has an x86 processor), and from what I can tell VSCode supports Ubuntu, the default Linux distribution for Crouton. You can even set up the Crouton Extension to put your GUI programs into Chrome tabs or windows within ChromeOS using Xiwi.
Anything with a GUI running in Crouton is going to hurt performance and battery life on Chromebook since ChromeOS is finely tuned for running specifically the Chrome Browser. I don't expect you run out and learn a terminal-based editor today if you haven't already, but I highly recommend at least getting comfortable using the terminal for quick editing, using git, and running simple shell commands. That will save you that sweet Chromebook battery life and a bit of frustration dealing with a somewhat-quirky Xiwi and Crouton Extension.
If you're willing to work out a few kinks the Chromebook Pro development experience is pretty great. It's truly a quality piece of hardware and ChromeOS is fantastic with the addition of the ability to run Android apps.
UPDATE (9/19/17):
There is another option now for at least getting server environments running on ChromeOS without using developer mode. It's called Termux, an Android app, which can bind to a local port and can be interfaced with via SSH. You can read more on the blog post we came across here: https://blog.lessonslearned.org/building-a-more-secure-development-chromebook/ You will, however, have to use a terminal-based text editor like VIM or a native ChromeOS one like Caret, so it will not run GUI editors like VSCode or Atom.
Check out https://coder.com
It's basically VS Code running on a remote server, accessible through a browser.
I've just started playing around with it and looks like a perfect fit for a Chromebook. And it's open source too :)
You can now (with the Linux-beta for chromeOS) quite easily run vscode locally on a chromebook, see this step-by-step guide: https://blogs.sap.com/2018/10/16/set-up-vs-code-on-chrome-os-for-local-application-programming-model-development/
On Windows desktop I use SocketTest as GUI tool to test TCP connections.
Is there alternative for Windows CE (native are preferred) to test connections with Windows Desktop?
The Winsock API (winsock 2.x at least) on Windows CE is quite similar to the one you've on "full" Windows. If those samples are not using too many advanced UI features porting them to CE won't be too complex. If the GUI part is not easy to convert you can still keep the low-level socked-related routines.
I want to test my web application on Internet Explorer 9 but I don't want to buy a copy of Vista/Win 7 on my developer machine with Windows XP.
Anyone knows a workaround, free and easy?
Use another machine.
Or better, get a set of Virtual Machines established which have an array of operating systems and browsers installed. Build enough VMs, and you are covered for all eventualities, regardless of whether you would personally use them or not.
Link to Internet Explorer Application Compatibility VirtualPC Images
You can't. The closest you'll get is IE9Preview.
I've found that IETester is not a bad way to quickly switch between browser versions for testing.
http://wiki.winehq.org/WineOnWindows
You can try running Wine on windows.
This will let you emulate a newer version of Windows
However, it will be really buggy (not mentioning how Wine is already buggy)
Its a unix/linux application ported for Windows
:)
IE 7,8,9
https://browserlab.adobe.com
Use
https://browserling.com
In unpaid version you have 3 minutes to test any site accessed from Internet on any browser.
In paid version you have unlimited sessions and ssh tunneling.
I'm using the Native Wifi API and specifically the function WlanGetNetworkBssList.
I am aware that that function is not available in Windows XP SP2 and SP3. I tried installing the hotfix that was supposedly to allow access to that function but it did not work.
So are there any Wireless Zero Configuration .NET wrappers out there?
Or more basically, how do I get a list of the basic service set (BSS) entries of the wireless network or networks on a given wireless LAN interface without the use of that function?
Did you have a look at how MetaGeek's InSSIDer does it. It's C#, and open source (Apache License and available on github).
This app is gorgeous and very useful. There are at least 3 versions.
InSSIDer
InSSIDer 2
InSSIDer forLinux
I've got a vintage XP SP3 here and it works pretty well. However, I do not think it relies on the WlanGetNetworkBssList API (it's close to the physical interface and besides, I'm using the Intel Wifi management stack (so my ZeroConf service is stopped) and InSSIDer still works).
There is open source WLAN API library which allows to obtain wireless BSSIDs on Windows XP SP1 and higher by using NDISUIO 5.1 or Wireless Zero Configuration service.
Original code is written in C++ but can be converted into C# for your needs.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
Which OS do you prefer to program on? Client or Server
There is a school of though that if you are doing (mostly) web programming (or other server based code), you should use a server OS for your dev machine, since that's closer to the environment where your app will be running.
Update: I should add, this is really directed to the Windows crowd
OK, I know you're mainly talking about windows but...
I used to develop on windows for deployment on *nix servers. Sure there were lots of gotchas with this way of working, but you just kind of get used to it.
In October 2005 I switched to Linux, initially as an experiment, but I never went back. There was a steep learning curve. I thought I knew *nix pretty well after 10 years of dealing with it, but I knew nothing compared with the amount I learned using it on my desktop machine.
Workflow has been so much smoother developing and deploying to similar platforms.
More recently, we have even started to pick servers running Ubuntu server, so that they most closely match our Ubuntu desktop development machines.
If you are talking about the difference between a desktop and a server edition, I'd guess you needn't worry about it. If you're developing on one OS for deployment on another, I'd consider changing your desktop platform.
There is a school of though that if you are doing (mostly) web programming (or other server based code), you should use a server OS for your dev machine
I think that applies more to 'system programmers' rather than web 'application programmers'. Why? There is definitely great value in knowing the platform intimately, like one would get in living with the OS, etc. day in and day out. But not everyone can or should need to go there.
While my main production environment is RHEL4, Linux just does not work for me on the desktop--in fact, it drives me crazy. I find working on OSX close enough, though. And I just love working on my Mac rather than an XP box.
I'm doing the Java thing, and the "write once, run everywhere" hype actually works for me. :)
Update: I should add, this is really directed to the Windows crowd
Minute late, bit short ;) Maybe you should edit the title too...
It seems like the question is more about whether to use the server or client version of the same OS. So my answer is this: the client should be just fine. You can develop and test web applications of many flavors on client versions of Windows, OS X, and Linux. OS X and Linux obviously make Apache-based apps a little easier by coming with Apache pre-installed, but a download of XAMPP or WAMPP can quickly turn a Windows box into a solid development platform for LAMP applications, as well.
And if you're doing ASP.NET, your development tools (if you're using something in the Visual Studio line) have test server mechanisms built in.
So unless you have some other need for wanting the server version, I would stick with the client. It's less money, and you really don't need the server version.
The client vs. server OS issue is only relevant on MS platforms. And even there it depends on what you're developing for.
As far as I understand for Sharepoint development you need a server OS to run your code
If you're just doing vanilla ASP.Net stuff then it's mostly personal taste.
Edit
As Tyler commented, you can run MOSS/WSS on Vista but it's not supported. Or you could develop on a client OS and run sharepoint on a server OS in a VM.
Regardless of the operating system you're actually talking about, it shouldn't matter. Most applications you might write won't need to worry about the differences (if there indeed are any). Only in rare cases might you use some specific functionality that might only be available on a "server" edition of your OS.
There are other considerations, for example Windows server editions are tuned by default to give less priority and attention to desktop programs, and more attention to things like the file cache. Personally, I would always choose a "client" edition of my chosen OS.
Personally I use Windows Vista but that's because it's what I like and I can use it well. But in all honesty it doesn't matter, your OS should be something you are comfortable in and has the tools you need to be productive.
I would say your test environment is the one you need to have as close to your production environment as possible. I write in RoR on Vista but test it in a Linux VM setup the same as my web server and at work we have a Win2k3 server with IIS6 installed to test our .Net sites on but I develop on Vista using IIS7.
I use Windows Server 2003 set up as a workstation.This is the guide i have used for several years. Really like it.
This is going to be a bit of a weird answer but I'm a big fan of Windows 2008 and Hyper-V, as a workstation (I know). Essentially I'll only install Office like software on my workstation and all the development will be in Virtual Machines.
Assuming there's no Win2k8/Hyper-V availiable I'd gladly settle for some old WinXP (but w/Virtual PC).
Hyper-V allows you to get great performance out of any .VHD VM that you run. Both Virtual PC and Virtual Server are free (as in beer) and you can set up a ton of infrastructure that allows you to re-purpose virtual machines (ie. Base Machines, Differencing Disks, Undo Disks). The .VHDs are also interchangeable so you can re-host a previously enjoyed .VHD for other developers to enjoy on some virtual server, OR they can take a copy of it, rename the virtual machine and enjoy your ready-to-go environment with some Virtual PC!
This is awesome for bringing team members up to speed (environment wise) in less than 10 min. YOu can also use it to VERY QUICKLY provision machines that would otherwise take days to setup/configure.
Never mind the much better ability to test from different OS', or be able to roll back changes using Undo disks, VMs are a life saver! Start virtualizing people!
For some of the great benefits of Virtual Machines/Differencing Disks consider this post by Andrew Connell.