I am developing Windows Store app using Visual Studio 2013 with update 5 in Windows 8.1, but now we move on to windows 10, and issue arise is responsive in XAML.
I want to know is it possible to design Windows Store application behavior is responsive with existing Visual Studio version 2013?
I explore it how to responsive Windows Store app, but Visual Studio gives this in VS version 2015 and 2017 like relative panels properties, and triggers etc. So, but I can do this in Visual Studio in 2013 version.
So much has changed since Windows 8.1...
You have options on how to go proceed that would depend on many factors - like your resources (time, people, money...) or the composition of your user base.
Your best bet might be to build a separate UI for Windows 10 and reuse mostly just the view models. Possibly simply move the 8.1 version on a back burner and only fix problems and continue working on Windows 10 version separately. This would save you from having too many test dimensions in your code to do API checks etc.
The careful and cheap option is to only add specific new features lighting up on new versions of the OS using API checks.
If what you're looking for is using relative panels and triggers while staying on VS 2013 - well, you don't. The thing is though - relative panels and triggers are only there to make things slightly simpler to do. You can still achieve similar or same results in Windows 8.1 with some custom code.
You can use separate templates for your UI and switch them when the size changes.
You can handle size changes in code behind and rearrange elements and properties from there.
You can build a custom VisualStateManager and/or custom panels that do the same things as you get from the responsive design features in Windows 10, although that's possibly writing a lot of throwaway code that you wouldn't need anymore as soon as you could move to newer versions of VS and drop support for older versions of the OS.
Related
I decided lately to move from Eclipse ADT to the latest AS version.
The first weird thing that I've noticed is that when I create a new project, it is always based on the Android support library even though I selected the minimum SDK to be level 19.
What is the reason for that?
Is there a way to configure it otherwise?
The reason for this is mainly backward compatibility. Right now, you may want to make your app for API19+, but later you may decide to lower it a bit down to support more devices, and you shouldn't be having problems with that, if you use support library.
There's also the thing that support library gets updated much more often than Android core library, therefore, if you base your project on it, it should be pretty much bug free.
One more thing, if you extend activity compat for example, the activity checks what version of Android you are currently having on your device and uses core features automatically if available, so it's good for you in many ways to use support library :)
I have a couple of Projects created in visual basic 6 with oracle databases. I want to upgrade these proejects to visual studio 2012 and use TFS version control. I have read that first I need to upgrade to Visual studio 2008 and then to Visual studio 2012.
Before going ahead with the upgrade ( I need to install Visual studio 2008 as well) I want to make sure this is a realistic approach. So
1. Does converting a vb6 project to VS 2012 ok or I will have to make a lot of changes to make things work?
2. After upgradation would I be able to use TFS for the projects?
TL;DR - yes, you'll need to make lots of changes regardless of how you choose to migrate. TFS question seems irrelevant to me. If you're setup to use TFS for projects, you can use it for these after upgrade as well.
The only reason to consider a 2-step upgrade that includes VS 2008 is that was the last version that included the migration tool built-in (ie, free). As others alluded to, those tools don't make pretty code but a mashup of VB6 and .Net. After trying a few times, I now personally find it simpler and more robust to recreate a new .Net version from scratch, but using the VB6 code as a template. I copy and paste as practical and then do Find/Replace to catch the majority of errors/warnings and then deal with all the others individually. If I have to convert another project, I may use 2008 once just to see what kind of issues the original code had or if there are any unusual situations/controls I'll need to deal with, but I would still start a new 2013 project from scratch. That gives me a better opportunity to improve it as well. You'd be replacing all the connecting code to Oracle anyway. I'd been using OO4O and moved to ODP.NET. If you used 2008, you would have to move to at least 2010 to use the latter in managed mode, which is great not having to load Oracle Client on each machine.
I'd be wary of upgrading VB 6 to VB.net using the automated tools. I did it back in the day (around 2003) when .net was just starting out and my memory is that it wasn't a pleasant experience.
The code produced by the upgrade wizard is a nasty mix of old VB conventions trim, instr and .net conventions. We also had a bunch of weird bugs. Sorry it was a long time ago and I can't remember any details. Only that we did it once for a small number of components, around 6 or 7 activex dll's. That experience was bad enough that we decided it wasn't worth the pain.
We kept the VB 6 code in service until it was re-written as part of a larger push to modernise the codebase.
If you do decide to upgrade then the output is a standard visual studio project that can be source controlled in TFS just like any .net project.
If you reason for upgrading to just to use TFS then take a look at the MSSCCIProvider. This allows you at hook TFS in to the VB6 IDE
I am doing something very similar and did develop a tool to assist with the designer portion of the conversion. It parsers the VB6 file and creates designer code for .NET.
The source is here.
https://github.com/rdejournett/VBtoNET
The only thing I was not able to solve is that controls within tab pages have really wierd X locations like -60000. So I parse those to 0. You'll have to move them to the right place.
I have a POS software and need to develop a collecting module for windows CE to run on a Honeywell Dolphin 6100 device.
I need to develop a simple application to run on a Honeywell 6100 device. This application should:
Get a list of products (code, description and price) from my POS software
Process Sales reading product's barcode showing Total due and number of items
Upload that sale to my POS software (via network, files, or something like that)
What are my options? Are there any Application builder for Windows CE? If not what could I use to develop such application?
You have a few options, but few (if any) of them will allow you to create the application without writing code. I'm aware of no "application builder" products that will get you there in Windows CE, and I've been working with CE for some time. That's not to say some obscure thing might not exist, but I am not aware of one.
You can write your application in .NET - either C# or VB.NET are supported - using the .NET Compact Framework (CF). For that you will need Visual Studio 2008 Professional and really little else, other than a device. There are lots of tutorials and online resources for CF development, so I won't put in a list of them here.
You can write your application in C/C++. For this, again you'd want to use Visual Studio 2008 Professional. Yes, there are options that use other compilers, but if you want to spend time actually writing the app and not building up a development tool chain and figuring out how to get it connected and debugging, then Visual Studio is the route you want.
If you'd like a non-Microsoft solution, there are others that are supported to more or less of a degree. NS Basic has been around a long time, so it's probably pretty robust and has reasonable support. I've never used it, but I've heard good things about it from those who have.
Anything else and you're a bit off the reservation. Support will likely be minimal at best, tooling will likely not be robust, support, tutorials and all of the other goodness that developers often rely on to move forward will be scant. You can likely get any language working under CE, given enough time and resources, but the options above are the most likely to lead to success.
Since you said you know Delphi and didn't want to learn another language, you can use Delphi Prism to write a client app to run on windows CE, pull the data you need, and post it to a webservice:
Is Delphi Prism a new version of Delphi .net?
http://en.wikipedia.org/wiki/Oxygene_(programming_language)
(edit) Just checked and it's now a part of this package:
http://www.embarcadero.com/products/rad-studio/faq
We're planning moving from Visual Studio 2005 to Visual Studio 2012 (Visual-C++-11).
(We would very much like to skip 2010 if we can help it, since the newer version is already there and offers a better C++ experience.)
But we've hit a little roadblock:
Our build servers still run Windows 2003r2 (all inside dedicated virtual machines), and due to messy tool support/issues, we're in no position to upgrade the build servers to a newer OS.
Developers mostly have switched to Windows7 by now, so moving the remaining Windows XP developer boxes shouldn't pose a problem.
Since VS2012 only runs on Win7 we are wondering whether we can leverage it's tools (C++ compiler, C#) and still do a full equivalent build on the W2k3 build server - after all, we don't really need a VS GUI there, just build C++ and C# projects from VS2012.
What are our options?
Will the SDK (7.1? 8?) compilers + msbuild command line get me anywhere?
In Project Property Pages, there an option "Platform Toolset" that allow you to choose compatibility of your project. So, you can work in VS2012, but built it with "VS2008 compiler"
Here is what we do:
Use CMake
CMake allows you to create build systems for your operating system. Thus we are able to use the same code within VS2005, VS2010 and Eclipse, XCode etc.
You could do something similar: Install VS2005 on your old machines and let CMake create the projects for you from the sources. On your newer machines you can use CMake to generate VS2012 Solutions (I don't know if they have 2012 support yet, because we don't use 2012 yet too).
A big pro here is: If you plan to migrate to any other IDE or even Linux you just can re-run CMake and get your source code within these environment easily compilable.
A big con: You have to start reading about CMake and create CMakeLists.txt for all your projects (might be a lot of work depending on the amount of projects, amount of source code files within each project, specific compiler options, linker options etc.)
Our build servers still run Windows 2003r2 (all inside dedicated
virtual machines), and due to messy tool support/issues, we're in no
position to upgrade the build servers to a newer OS.
Well. Not much came out of this question. We recently re-evaluated this issue, and I see two options (I haven't tried any yet):
Just do a full VS installation on a supported OS (Win7), zip up the whole VS+WinSDK directories (as well as the neccesary runtme DLLs that live somewhere under %WINDR%), and try if you can get that thing working on an XP based OS. Might work. Not a great idea if you ask me.
Split up the build process to distribute the build across several OS, so that we can work with tools that are only supported on one of them. -- This actually sounds more complicated than it'll be. We already run our build spread over several Jenkins jobs, so I should be able to get that to work. (And all build nodes are already VMs anyway, so adding more VMs isn't that much of an issue.)
According to Microsoft Visual Studio will no longer support setup projects, requiring instead that developers download and register for a light version of InstallShield.
Does anyone know if there are alternatives out there - WiX comes to mind but in a way this is like going assembly...
Wix. it is not like assembly, it wrocks - especially compared to installshield.
Otherwise no - before Wix came around installers where a bad area to be in anyway. Only buggy products, choose your pain between Installshield and Wise installer (now Symantec Altiris).
I prefer Wix any day over the other stuff.