|
Straight to the point:
I have a WinForms app I've written years ago that persists some settings to a local file. A subset of these would be useful to share across a few of my machines.
I'd like to have some of these settings persisted to something like OneDrive, so a copy of my app running on multiple machines have those settings available to them - change a setting once, and all the machines see the new value the next time they launch (assuming the user provides his OneDrive account credentials).
I've never looked into the OneDrive SDK, so I'm going to ask the question like a naïve user: Is OneDrive appropriate for this? Overkill? Square peg in a round hole? Ultimately I want to give OneDrive a simple string (say, XML) and have it take care of persisting it. Then any of my machines using the same account would have access to the same string. So what's the minimum that needs to be done, architecturally, to make this happen?
|
|
|
|
|
dandy72 wrote: Ultimately I want to give OneDrive a simple string (say, XML) and have it take care of persisting it.
That would fit more with a web server than a document store.
However looks like you could sort of do that based on what you mean by "give"
OneDrive Dev Center - Develop with the OneDrive API[^]
|
|
|
|
|
jschell wrote: That would fit more with a web server than a document store.
"Web server" is such a generic term.
OneDrive's infrastructure is already in place, scales, and its maintenance is essentially somebody else's problem. I just want go be able to log into a bunch of my machines, and the app I run on all of them needs access to settings that should be common among all instances that I've associated with that account.
Thanks for the link. It looks familiar, so I've probably come across it before. Something tells me I have an awful lot of reading material to go through just to decide whether this is something that makes sense to use or not.
|
|
|
|
|
I would assume that you can discover if the local machine has a onedrive mapped, supplying credentials to a mapped drive is trivial. If you own the onedrive you should be able to find a location and get at a settings file.
It would get a little more interesting if you need to get someone elses onedrive account to share a folder on your account!
As JSchell pointed out a WCF running on a web/intranet would actually be simpler.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
I was thinking about a question[^] asked in QA..
Rather than mapping PCOC's/DTO's across multiple projects, I typically create an Entities project in my solution and reference it from all other projects that need it. One set of classes is much easier to maintain IMO.
So, given that, any reason not to make these classes all serializable as well as implement INotifyPropertyChanged?
I don't see any issues with this. Anyone else?
If it's not broken, fix it until it is
|
|
|
|
|
Kevin Marois wrote: I don't see any issues with this.
If you can generate the bulk of the code or abstract it away, go ahead.
Might cost a bit more performance, might be raising an INotifyPropertyChanged without the code doing much with it, might introduce a bit overhead.. but would save time in having to implement it and/or update/change its implementation.
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
This is exactly the design we use, including the OnPropertyChange event. The "models" project is then referenced by both the WCF and the WPF/Silverlight projects. Seems to work perfectly for us and we have more than 18 apps in production.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
I think there is a tool in Visual Studio to help tester to do image and video capture of they step during manual testing. Could you help me to find more information about it?
I think I use bad keyword in Bing/Google because I find many information about debugging but nothing specific to VS.
Thank you,
|
|
|
|
|
Nothing that I've seen in Visual Studio. Are you thinking of the Problem Steps Recorder[^], which has been part of Windows since v7?
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
|
Create a modulo-k counter by modifying the design of an 8-bit counter to contain an additional parameter. The
counter should count from 0 to k − 1. When the counter reaches the value k − 1, then the next counter value should
be 0. Include an output from the counter called rollover and set this output to 1 in the clock cycle where the count
value is equal to k − 1.
Perform the following steps:
1. Create a new Quartus II project which will be used to implement the desired circuit on your DE-series board.
2. Write a Verilog file that specifies the circuit for n = 8 and k = 20. Your circuit should use pushbutton KEY0
as an asynchronous reset and KEY1 as a manual clock input. The contents of the counter should be displayed
on the red lights LEDR7−0 , and the rollover signal should be displayed on the last LED. This is the LEDR9
for DE0-CV and DE1-SoC and the LEDR17 for DE2-115.
3. Include the VHDL file in your project and compile the circuit.
4. Simulate the designed circuit to verify its functionality.
5. Make the necessary pin assignments needed to implement the circuit on your DE-series board, and compile
the circuit.
6. Verify that your circuit works correctly by observing the lights.
modified 12-Jan-16 11:38am.
|
|
|
|
|
This looks like homework and nobody here will do it for you.
If you have a specific problem show us what you have tried so far and where you got stuck and you might get help.
But your question is related to a specific VHDL device and there might be not so many people here that are able to answer.
|
|
|
|
|
How can I get social networking/question answer site programming tutorial?
|
|
|
|
|
By searching with Google.
|
|
|
|
|
I did but nothing came out
|
|
|
|
|
Well that should tell you that no one has yet written one.
|
|
|
|
|
I am working on building a C#.Net winforms project using Entity Framework 5. Currently, I have Model.edmx file on a separate project (DAL) and in my UI layer, I am instantiating Model and accessing my entities, however, I would like to create a proper 3 tier architeture, where separation of concer is adhered to.
Data access layer (where Model.edmx is kept)
Business layer (where Model.edmx is instantiated etc.)
UI layer (all forms code is kept)
Any pointers? Or samples?
|
|
|
|
|
Resonate wrote: Any pointers?
Question is too broad.
People don't write application based on technologies. Rather they write applications to solve problems and use technologies as appropriate to solve the problem at hand.
If this is just a learning experience then there are simple examples which you can google for to learn the idiom. Best practice however doesn't come about from simple examples.
|
|
|
|
|
I'm working on a project that should bring together multiple "services" we offer together into one webpage. These services are basically different (long term) projects that provide different kinds of data. images, videos, "objects"(*), plain text, timeline data, ...
So the main architecture would be to write an interface that would serve the project's webpage, but also could be reused for other projects (so not only that webpage).
The current discussion is whether to use JSON, XML or web services. I'm looking for advantages/disadvantages for all three.
Personally I would opt for webservices. type-safe, most flexible and especially, no parsing  (in the sense that the IDE will interpret the wsdl for you). There is a learning curve for non-programmers and apparently php and web services don't mix well I'm told. (Most people here use php to do something code-wise). They use Python as well and I know that works and java is also used often. (I personally don't know php)
XML seems like a good alternative since you can create validation schemes (and make it more or less type-safe) and there are many libraries that can handle it reasonably well. It is a very verbose format.
JSON is very lightweight and easy understandable, but is less type-safe and no validation scheme to my knowledge.
So what is your thought on this? Any good read-ups on pro's and cons out there would also help.
thanks!
(*) Objects with attributes, a structured set of data belonging together.
|
|
|
|
|
Can all your prospective clients consume your transport format, if yes then use JSON, the sheer verbosity of XML can kill your network/server. That schema comes at a very high cost if you are transporting high volume or complex data.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
IIS can perform dynamic data compression; and XML can compress to less than 10% of its original size.
I talked one sports analysis vendor out of upgrading their transport layer by showing the reduction in bandwidth that compressing their XML game files would accomplish (which ranged up to several hundred megabytes uncompressed).
There is no generalization when it comes to transporting XML versus JSON in this case.
|
|
|
|
|
And if they aren't using IIS? Okay, that's slightly facetious as the other major web servers all offer similar functionality but it's always worth remembering that, where the poster hasn't specified a technology stack, that you can't assume a particular feature is available.
This space for rent
|
|
|
|
|
Certainly.
But that's why I said "IIS"; and not "some web servers".
(One Google also told me Apache does compression ... Any others worth considering? WebSphere?).
I could have also argued that "protocols" (XML and JSON) are not the same as "web services"; and it's not like you pick "one of these".
And also about how I could use compressed "payloads" (which I already deal with when communicating with web services that supply graphics).
(It's not like I was going on about something totally unrelated to the question; like, "SQL injection" ... again).
|
|
|
|
|
I would vote for WSDL (SOAP?) based services...and PHP has no problem whatsoever to work with that...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Kornfeld Eliyahu Peter wrote: PHP has no problem whatsoever to work with that
I was indeed surprised when told. WSDL would be my first choice as well, but the people here don't like it for some reason (not standard, unlogical, verbose, ... ). I'm trying to convince them this is the way to go so I need arguments 
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
