|
but I didn't now how build and create Internet-accessible server
|
|
|
|
|
1. take computer
2. plug in cable to router
3. ????
4. profit
(Part 3 also includes setting up port forwarding, and your ISP agreement needs to include a fixed domain name or (ideally) IP.)
You can also use a hosting service or a cloud service like Amazon's that will give you public IPs.
If you don't know about this, you probably shouldn't be trying to create Internet applications, because it's odds on that you will make dumb security mistakes as well.
|
|
|
|
|
thanks for avadence and help mr:BobJanova
|
|
|
|
|
I have a web page that needs to generate a report for download on a hosted server. Because of the complexity of the long running report I was thinking it would be best to have this run as a service. My thought was that it would work like this:
1. User initiates request for report through web page which sends request to service or application.
2. Service or Application generates report on server in background.
3. Service or Application saves report as PDF.
4. Service or Application emails notification upon completion.
At any time during the process the user should be able to visit a processing page that gives them the status of the report generation.
With that said, does anyone have direction for me on what to do with this? I have never built a web service or an external application for something like this, but rather embedded all my reports within my application so I am a bit lost on where to begin.
While I realize that this is not strictly C#, it is going to be a C# item, not an ASP.NET page. Any help is good help.
Cheers, --EA
|
|
|
|
|
There are other issues such as
- Exactly how long does it take to run
- What about duplicate request
- What happens if there is an error while it is running.
Presumably you are also assuming that the email will always reach the target.
If it was me.
1. Create windows service.
2. Post the report request into the database as a 'task' - invalidate duplicates.
3. Service looks for new requests.
4. Service process new requests.
5. Service posts results, either report or failure reason back to database updating the 'task' (so it won't run again.
6. Post process - like send the email with results.
7. Go back to step 3.
There might be some clever way to embed the functionality in IIS.
|
|
|
|
|
It depends how long is 'long'. For fairly long but not ridiculously so (or that processor intensive), you can just start a new thread in your web app to handle a report (or, better, use a thread pool, BackgroundWorker or Task to manage resources for you). If you need to farm it out to a different process, perhaps on another computer, then personally I would manage the communication through a TCP connection between processes. I wouldn't put the report status in a database table as that data is transient (only relevant while a report is being constructed), unless you need to audit the report generation pipeline. You could also do it with pipes or WCF or DDE (yes it still works!) or any other form of inter-process communication you're familiar with, depending on your OS.
However you manage that part, you then need a page which spawns a new report processing unit (thread or process) or adds a report request to the queue of an existing one, a page which will look up the status of an existing report (so you need to give your reports queryable application-unique IDs) and some communication between the web app and the processing unit to maintain information about the status of outstanding reports.
|
|
|
|
|
I want to open a msg file from disk and perform a Reply action like normal mailitem and display it to user.
Currently i have a datagrid where i show list of msg files .When i right-click on the grid we have context menu for Reply/ReplyAll/Forward option. If a user clicks on any of these action i should be able to open the mailitem in reply/replyall/forward mode.
In Outlook when we click reply for a mailitem it displays the mailitem to user...the same way i want the msg file to be opened to user in reply mode.
Any help is greatly appreciated ... 
|
|
|
|
|
Hi all,
I am creating the setup for my windows application,i want to include the expiry date for it that means whenever the setup is installed it should run for the 30 days after installation.
How can i do it ?
Is there any script in c# ?
Thanks in advance.
|
|
|
|
|
The way you could tackle this requires quite a bit of infrastructure you probably haven't got in place yet. Basically, when your application starts for the first time you would register it on a remote server (use a web service for this, and generate a unique ID for the app). Using this ID, every time the application is run, compare the expiry date with the current date at the remote server and return whether or not the application is run. The advantage of this approach is that it takes into account the user resetting their system clock trying to circumvent the time check.
|
|
|
|
|
Disadvantage for this strategy is that user must have a network connection which is always connected.
|
|
|
|
|
or at a site that blocks it (corporate firewalls etc)
|
|
|
|
|
Or they wireshark the "it's ok, run" response from the server, redirect the server domain to localhost, and then run the program forever using a fake server.
Or they'll just remove that check from the program, which is probably a lot simpler.
|
|
|
|
|
Or share the ID amongst several installations.
|
|
|
|
|
|
Better way is something like writing a hidden entry in registry or somewhere else.Keep updating the time at some events.Check whether the user is tampering with system Date , if he is doing some trick like this, expire the appln.Else run it for 30 days.
|
|
|
|
|
This isn't a better way, just another way. It also isn't secure, it is possible to download free registry watchers to see what is being changed. Checking whether the system date has changed is a problem too, as this can be done via the BIOS.
For .net apps there is no 100% way to secure against tampering, the best you can hope for is to stop the majority of users.
|
|
|
|
|
It's not worth the trouble. Just write the first version of the application, give it away for free, and see whether or not anyone likes it. If it becomes popular, maybe see about adding such things for version two. If not, at least you didn't waste your time.
|
|
|
|
|
I would write a registry value somewhere non-obvious on first use of the application with an encoded timestamp in it. You could also write an opaquely-named file into a system folder but since UAC it is not a given that you will be allowed to do that.
Any check of this kind you put on your application, particularly if it's written in .Net, will be pretty easy to find and remove, so don't put a lot of effort into it. But this kind of simple check is sufficient to tell people you'd rather they paid, and to protect the app from the vast majority of lazy users.
That said, you should strongly consider releasing software for free these days. Payware stands a good chance of turning people away, and the goodwill and potential future work you get from a quality free tool may well be worth more than the limited number of sales you'll get. And there's no need to try to protect free stuff.
|
|
|
|
|
hello guys... I have these two forms say From1 and Form2. Now I have some controls on Form1 and a datagrid on Form2. When I select a record from grid on Form2, I want this record to be shown on Form1.
Now I have got the data and saved it in the class - say DataClass.
DataClass data = new DataClass();
data.Id = Id;
data.Name = Name
. . .
But the problem is: how would I know user clicked the Select button or Close button, on Form2. Of course I wanna show data only when user clicks Select button. How can I do this? thnx
|
|
|
|
|
Have you opened Form2 using ShowDialog()? If you have, just check the result for DialogResult.OK which equates to clicking the OK button. Then all you need to is retrieve the data from a property that you have exposed in Form2 that contains the data.
BTW - please give your forms meaningful names; there is nothing worse than having to maintain a project where everything has default names because it means you have to open everything just to find a particular form.
Hmm, I'm not sure why you were voted 1. I have balanced the vote out somewhat.
|
|
|
|
|
Actually it does not have the button OK, it has the button Select. So I dont know how your solution us going to map here. Any guidance in this regard will be appreciated.
I actually have meaningful names for my forms but to keep the question simple, I said them Form1 and Form2
|
|
|
|
|
It doesn't matter what the text says - all you need to do is set its DialogResult to OK.
|
|
|
|
|
In teclick event of the grid , create a new instance of form1 with an overloaded constructor of Form1.make DataClass as the parameter , then Show form from there.Done
|
|
|
|
|
So now he has two form1 instances running. I don't think that's the effect he's after.
|
|
|
|
|
There are two ways to do this, either by public/internal properties in Form2 or passing an instance of a custom class derived from EventArgs. Either will require some kind of signalling to Form1 that the data is ready.
As previously mentioned, if Form1 shows Form2 via ShowDialog() then you can expose a property in Form2, set the DialogResult of Form2 to DialogResult.OK and check for that as a result of the ShowDialog() call, accessing the property.
This same procedure can also be done by subscribing to Form2s FormClosing event, although the dialog result is a better alternative as you have information relating to the success/failure of user interaction.
Alternatively, Form2 can raise a custom event subscribed to by Form1. If using this method (the one I prefer) then you can pass a custom event args class instance along with the event that contains only the relevant data - nice and clean and no need to expose properties in Form2 to the whole world.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
