I have two Windows form applications using C#. One is for acquiring data from a spectrometer. This application includes lots of references and assembly files require to interface Ocean Optics spectrometer with Visual Studio 2012
Another application which send this data to Mathematica tool for signal processing and retrieve back result and display it on UI of second application.
I want to integrate these two apps' UIs into one UI, so that from the single UI front end, I will be able to acquire and send data to Mathematica and retrieve back the result and display it on the UI.
Related
Hi and thanks in advance.
I'm experimenting with a Xamarin.Forms app to handle various events organized by my company (one a month), and I'm taking a cue from the great app made by Xamarin for Evolve16.
But I don't understand how I can populate the database created in Azure backend with code first. I know there is a Seed method to eventually do this the first time but next? Every month I need to add new data (for example new sessions) quickly, and I do not want to provide this functionality within the app because the app should only provide contents to users. All domain obejects inherit from EntityData so I don't know if I can use LINQPad or SSMS to insert data directly because there are fields populated automatically (Version, CreatedAt, UpdatedAt...). Can I use rest api of backend table controllers? But where is the "try out" possibility that there was in Azure Mobile Service??
There are several ways to answer this. Basically, you want to alter the underlying tables in the SQL database
1) aka "the simple version" - download the SQL Server Management Studio and do raw inserts into the table
2) aka "the separate website" - write an ASP.NET web app that uses Entity Framework to do the inserts for you. Make sure you include the Azure Mobile Apps Server SDK and make your models inherit from EntityData.
3) aka "the combined website" - download the Node project that underlies the service and adjust it to add your own website that can do the inserts for you.
The "try out" option is now implemented with swagger. Just go to https://yoursite.azurewebsites.net/swagger
I am creating a application which is mainly used inside a office for data maintenance. It will be used to store data like work list, future works, reminders etc .All data will be presented to user in the form of grids. So it's all about data stored in SQL server database. There will be number of users accessing it and they modify data frequently. Also there will be so many options like an ERP program.There is no connection to internet is required for this program.
So in this case which programming language is better? Should I choose WinForms or ASP.NET? The main concentration to choose between this will be performance, ease of use, also it should support more function for grid controls etc. So which one should I choose? And what will be the advantage and disadvantage of both?
Some pointers:
WinForms
Good
No webserver to install, setup and secure
Bad
Installation of some kind required on each machine e.g .NET framwork, exe, assemblies, etc.
More difficult to rollout updates to the application
ASP.NET
Good
No installation on clients required
Can run on machines other than windows including mobile devices
Updates to the application can be published instantly to all clients
Bad
Have to use IIS or UltiDev Web Server to serve up pages
File system is more secure so reading and writing to files can be time consuming to configure
Unless you want to use jQuery and Javascript to add additional functionality to the Standard ASP.NET GridView I would say a Windows Form would be more suited, depending on the size of the data it will most likely offer better performance and you have much more control over the actual functionality of the program, rather than dealing with browser related restraints.
Not really a question for this forum... VB.Net is a Language and ASP.Net is a Framework. Do you mean should I create a client windows app or a web (intranet) app then this would depend on your strengths as the intranet option would also require HTML and possibly CSS/Javascript.
I have data in sharepoint which has 104 columns and 708 rows. This data is basically contains information about enterprise. The senior management wants to view different charts by using these data such as bar chart, pie chart, tabular, bubble chart etc., There are no specific number of charts as they can plot any column against anything. For instance grouping of applications by criticality in a pie chart.
In order to create these n number of reports what we thought is to transfer the sharepoint list to sql server (using SSIS) and then use sql server reporting services (SSRS) to generate those reports and then use an ASP .net front end to contain the reports.
The very first important question is whether we can transfer sharepoint list to SQL Server using SSIS. Is this possible?
I think it is possible to pull SharePoint data using SSIS but I have never done it personally. If you are using SSIS 2008, following links might help you.
SharePoint List Source and Destination
Extracting and Loading SharePoint Data in SQL Server Integration Services
Our commercial product "Enesys RS Data Extension", a reporting services extension, lets your build reports directly from your SharePoint lists.
Not sure it would provide much benefits to transfer your list(s) to SQL Server first. If that's really what you would like to do however, the Standard and Enterprise editions also include "Enesys IS Data Extension" which offer a set of components for Integration Services.
You can also use the "Connect to Access" button from a list to put a copy in Access and then use Access's export to ODBC Data Source to move it into a table in SQL. Very quick and easy.
I have a customer requirement where they would like to have different windows of a web application on 2 different displays (monitors): data lookup and entry on one screen and a document viewer on the other. The document viewer will be Flash or Silverlight based and loaded in a webpage. The app will be at least partially based on SharePoint. There is a need for communication between the two windows: when for instance a new task is clicked in the "data" view, the accompanying document needs to be opened in the other one.
The difficulties as far as I can determine:
Opening the two windows from within a web app
Actively position the windows on the 2 displays
communication between the two windows
as robust a solution as possible from a user perspective (e.g., re-opening a closed window, tracking changes between them, etc.)
I am looking for pointers in getting this done. I understand that I can launch the second window from Javascript, but that does not give me a lot of control over it. This solution will run in a closed, controlled environment, so limiting the solution to a specific browser (preferably IE8+) or the need to install additional software/components is no problem.
If i were you i would implement this with silverlight and asp.net mvc.
create a state object which describes the state of the 2 windows, this can be consumed and updated by both the silverlight app via web services, and the mvc app via javascript, postbacks or web services.
I'm working on a UI for a simple inventory system. The users will use a USB barcode scanner to retrieve an ID and then either retrieve information from the database about the scanned object or enter the new information. This will only be used within our corporate environment. I can't decide which is the best way to go with this. I would like to use this opportunity to take a crack at WPF.
I like the idea of having the users interact with a webpage but I don't like the idea of using the USB scanner as a keyboard wedge. I would rather use the service object so that I can capture the event. I thought about writing it as an XBAP running from our server but wasn't sure if it'd be able to interact with the scanner.
I want the flexibility to run this on any computer in the shop without having to install software locally and worry about different versions floating around. I would greatly appreciate some advice on this.
I would use ClickOnce Deployment.
I know you said you don't want to install anything locally, but it does take care of automatically updating the clients from a central location such as web server or file share. You can easily publish new builds right from Visual Studio. Each time the user starts the program locally it checks for updates and installs them, fairly transparently.
This would just be the UI and barcode interface, you could create a WCF service on the server for the actual work, i.e. database querying, business logic, etc.
We were in an almost identical situation in our shop, except it was a time-tracking application. We came up with a Windows Form application deployed via ClickOnce using a WCF service on the server. Its been working well and we don't need to go to each workstation to perform updates.