Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
As per my understanding, DNX (.Net execution environment) is provided to support cross platform web applications, which sounds good but it would be more useful if it were to support desktop applications.
Why would you need a cross platform web based application ? usually a web application/web site is hosted once and it shouldn't be an issue to host it on IIS on a windows machine. Is there something with DNX that I am completely missing or is it somewhat useful for desktop/console based applications as well.
What if you had a web-based application that you intended to run on both embedded devices like a Raspberry Pi as well as more conventional servers? The Pi may not be able to run a full Windows installation and thus may need to run Mono or some alternative solution.
The idea of a previous place was to have a self-configured, low power solution for doing some tracking through RFID. The embedded devices would have to have a scaled down version of the system but be able to synchronize with the bigger systems as there could be various reports and other data to be generated on the big servers in the overall system. Imagine tracking wildlife or a big farmer's field with various sensors that could report the data that then has to get sent up to the big central DB so data can be compared over time with bigger resources than the embedded device would have. Thus, you could have a dozen or so of the small embedded devices in the field and have a beefy server back at a home base that could generate reports, maintain dashboards, etc. from traditional infrastructure in terms of electricity, connectivity, etc.
There was also the potential for this to lead to something like Skynet if the embedded devices could form a collective consciousness but the project never got to that stage of things.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
I have made windows application in visual studio 2010 in windows 7.
Will it work properly in other OS version (like windows XP, windows 8, etc..)?
I have used third party DLL as reference for HID connection in application.
If there are c# controls which will behave differently depend on OS version, then please give list of them with details.
Thank you.
You should test on all the platforms you intend to support. Different O/S versions are, well, different (otherwise what's the point of them?), so you can't assume it will work the same way on each version. You may even find that things like the Service Pack version have an effect, or the version of other libraries available on the system (e.g. .NET framework in your case) can have an effect.
So, you should decide what platforms, with what minimum specs, you can support (from a technical point of view) and which of those platforms you are willing to put the time, effort and cost into supporting, for what period of time, and then plan to test thoroughly on all those platforms. And then repeat for each release of your software (so you might want to outline the support lifetime of each release in advance, so customers are prepared for when they need to upgrade).
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
Say I coded some application in C# using visual studio. Is there anyway I can take this application and embed it into a website so folks can use it from a website in the same way I would use it from my desktop?
If you coded a console application - no.
If you coded a winforms application - no.
If you coded a WPF application - yes
Two options:
Migrate it to silver light and it will only work on browsers which can install the silver light plug in. keep in mind that silver light is being disbanded by Microsoft, so it is not considered a recommended practice anymore even by MS. also consider that not everyone would agree to install silver light plugin for their browser.
You can also migrate your WPF to become a browser application - but this will require the client machine to have .Net installed on it - so this is like a replacement solution to what once was achieved by ActiveX technology.
Main difference between those two options is that the 1st one is cross-platform/cross-browser solution and the 2nd one is not.. however this might change in the future as .net is becoming available to Linux too..
If you coded ASP.Net - it is already designed for developing web applications.
I'm not sure what exactly you are trying to achieve but I think the WPF/Browser APP is what you looking for, you can read more about it in How to: Create a New WPF Browser Application Project
Edit:
I thought I'd mention if you have a Console or Winform app that people wish to use remotely (ie via a web browser) don't forget they can use Remote Desktop to access the application. Many large enterprises do this using Citrix. Often this is more practical when the cost of rewriting legacy applications is not feasible.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
We currently have a single database with users, customers, products and orders logically separated by schemas. We then have several MVC.net applications accessing the database via their own BLLs. Each of these applications have their own functionality and share some aspects with some/all of the other applications.
Currently, some code is duplicated in these BLLs and it's a bit of a mess to maintain. It does however, allow us to develop features quickly and deploy each application independently (assuming on major database work here).
We have started to develop a single access layer, properly separated out that sits above the database and is used by all of our MVC.net applications. Logically this makes sense as we can now share code between our applications. For example, application A can retrieve a customer record in the same way as application B. The issue comes when we want to deploy an application, we wouldn't be able to deploy one application, we'd need to deploy them all.
What other architectural approaches could we consider that would allow us to share code between our applications and deploy those applications independently?
A common solution is to factor out services (based on an arbitrary communication layer REST, WCF, Message Bus, your choice with versioning) and deploy these services to your infrastructure as standalone services.
Now you can evolve, scale and deploy your services independently of the consumers. Instead of deploying all applications you now only have to deploy the changed services (side-by-side with the old ones) and the new application.
This adds quite a lot of complexity around service versioning, configuration management, integration testing, a little communication overhead etc. So you have to balance the pros and cons. There are quite a bunch of articles on the net how to build such an architecture.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I'm trying to build software for property management, which includes full accounting support, document storage, client data handling and mail merge functionality.
I want to work with the smallest arsenal of tools that I'll need for the job - the simpler the better! It won't be graphics-intensive and support for multimedia is not required, but I would really like remote access.
95% of usage will be by property managers through their local desktop installations.
5% will be by owners, who want to check their account balance online, and change their personal details in the DB. There can be no installation for this.
Will asp.net suffice for this 5% remote access?
I only have a small amount of experience with winforms, and could learn asp.net if that's what I need for the remote access. My question is: Will this be enough for my objectives, or am I going to kick myself halfway through for not using something else? (WPF, Silverlight etc)
Thank you. I did ask this https://stackoverflow.com/questions/22628436/c-sharp-property-management-database-software-should-i-use-wpf-winforms-or-si earlier but didn't receive satisfactory results, and have changed my question slightly.
EDIT:
By data processing I mean running functions like "charge all 2,000 owners in the system a management fee increase of 5%" or "process all creditor payments into a batch banking file".
First of all, don't go for WinForms and Silverlight,
WPF is much more useful than WinForms
likewise ASP.net or ASP.net MVC based applications are more useful than Silverlight based web applications. And if you are planning to go for a web based solution, choose ASP.net MVC.
Now, concerning your decision to choose between desktop and web based solutions, I would personally suggest to go for a web based solution if there is no specific requirement which holds you going online. Also Google on pros and cons of web and desktop applications and this link.
And if you find out that a desktop application suits you, then develop it in WPF not in WinForms.
:)
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
We're a development dept that have 'inherited' a large BizTalk based middle-ware system (100+ orchestrations that run a large number of financial transactions).
The system is based on BizTalk 2003 which is now reaching end of life and our systems team want to can it.
Is is possible to migrate from BizTalk 2003/2004 to Appfabric?
I presume if we took this approach we'd have to re-develop the orchestrations to Windows Workflow (which we already use)
Or is a migration to BizTalk 2013 an better (easier) option?
Has anyone come across this situation before?
Thanks
Steve.
The two pieces of software have nothing in common, except that they both use the WF libraries.
AppFabric is a set of services, one of which is to host WF workflows. The workflows themselves are plain low-level WF4 workflows. No special activities or adapters to other systems like Biztalk.
BizTalk is a server product with rules, adapters to various systems, able to read various business process languages, define orchestrations at a high level,etc, etc
It's almost like comparing IL to LINQ. Yes, there is common ground but not much.