I wanted to create more than one application run simultaneously in Blackberry JDE4.5 can any one help me how to do it.
With the JDE all Active projects in your workspace will be automatically built (and deployed to the simulator when you debug). To see a list of Active projects, pick Set Active Projects from the Project menu in the JDE. You can also activate/deactivate projects by right clicking on them in the tree.
Related
I have a MVC 5 solution in VS 2017 with 2 projects. Sometimes, when I'm working in one, I need to enter new information in the database using the other one. The only way I know of doing this is to stop debugging, assign the other project as the startup, run it, enter the info and then reverse the process again. Is there a way that I can access the project (which is light, not too complex) without stopping the current assigned startup project ?
Yes. Right click on the project and select Debug > Start New Instance from the menu
If you right click on the solution name in the solution explorer, there's an option for Set Startup Projects. You can then select what you want to start when you run the application.
It's also under the Project menu.
Is it possible for me to run multiple (2) projects at the same time?
I realize that you only have the option of making a single project the 'startup project'.
But I have 2 web projects in my solution, and I need to run both at the same time.
Is the only option opening multiple instances of VS?
Right-Click on your solution (Top-Most node in your Solution
Explorer)
Click on "Properties"
On the right panel, expand
"Common properties", and click on "Startup Project"
Click on "Multiple Startup Projects"
In the "Action" column, select "Start" on the project you want to start
Optionally, you can change the startup order by clicking on a project and moving it with the arrows on the right.
What I do is open another instance of VS and have each project open in the separate VS windows. Then I run both of them.
This saves the hassle of having to deal with changing the settings around.
I have a project in Xamarin.iOS and I want to build it for different clients under different app ids with unique icons for each client. What is the best way to do this ?
There are many (many...) ways you could do this.
An easy one would be to create several application projects (.csproj) under the same solution (.sln).
Each project would have it's own configuration, defines, targets, even files (like icons). All sources would be links (i.e. file linking) from the master project.
That would allow you to customize/brand, build and publish each application separately, while maintaining a single code base across all of them (from a single solution).
The XCode documentation on the concepts of Targets and Projects are helpful, but still I am not certain on the best practices to use in my situation.
I have an existing codebase (used for Windows as well as iOS) in a single SVN repository, which has just been refactored from one single test application into a central library and an application. The idea is more applications will use this central library over time.
An XCode project maps one set of source files to one or more targets, so I could have a single project for my whole codebase and one target for the library and one for each app. However each app will obviously have its own code, so it seems a bit clunky to throw all the source into a single project this way.
Alternatively I could have a workspace with multiple projects, each having a single target. This is much more how I have things set up for the Windows build, where a Visual Studio solution corresponds to the Xcode workspace, and a VC++ project would map neatly against how XCode projects are organised.
But are there 'normal' / expected ways to do things in this kind of situation, some unofficial standards I should try to follow so other developers don't get confused?
Targets nowadays are used to build dependencies and separate builds within a project. You'll see it being used mainly for unit testing. Occasionally, you might have different binaries available to different processors or operating systems, but this is a rarity in today's app store world.
Generally, you'd have one project for each executable. This allows it to be worked on independently and compiled separately without interfering with each other.
You can include projects within projects, which allows you to work on them independently and set up dependencies for them. You can set up a project to build a sub-project and deposit it's executable in a location for your project to link to.
I would say for your situation, make a library project with executable and testing targets. Then include that project in other projects and you can link to or move the files to your other project's location. Here's the gist of how to do it.
I know you don't mention them, but workspaces were basically added to allow you to have multiple projects open in a single window. You can have all your test applications and reference code available without them compiling in the background as well. I find it super handy.
The key difference is that each target is in exactly one project, but one project can be a part of many workspaces. This lets you have projects Lib, AppA, and AppB, and then WorkspaceA = [AppA, Lib] and WorkspaceB = [AppB, Lib], so that developers working on AppA don't have to load stuff related to AppB. As a general recommendation it's a good idea to create projects for things that you might want to share independently.
When I share code between one or more projects (be it Xcode or another IDE), I typically compile the shared parts into a binary and then link it to the code specific projects.
In your setup, something like an Xcode project just to compile a dylib from shared C++ files, and then a main Xcode project that links with this dylib.
Ok, so I'm a total newbie to TFS and automated builds. I see how to set up a CI build in TFS pretty easily, along with the drop folder for output files. However, my solution has two UI projects in it. One is our main website, the other is a mobile site.
When developers check in, basically what I want to happen is for a CI build to fire, and then publish the "mobile" project to one server and the "website" project to another.
On a very high level, what steps do I need to take to make this happen? I'm not looking for a detailed explanation, I can Google individual things as needed I just want to know the basic process and what tools are leveraged to make this happen.
The easiest way would be to have two different builds set up to fire on check in.
First, in your configuration manager create two new configurations. One for the Mobile site and another for the main website. The mobile site configuration shouldn't bother to build the website and vice versa.
Then create two builds. For each build, set the 1.Required > Items to Build > Configurations to Build settings to pick the appropriate config to build.
Update your deployment locations as necessary.