Click here to Skip to main content
15,903,362 members
Please Sign up or sign in to vote.
3.67/5 (2 votes)
See more:
Good Morning:

I am looking for the best approach to architecting or designing the project below in .Net. Also, which tool(s) are best (Visual Studio, MVC, WCF, etc.)? Any good resources you can point me to (sites, books, etc.)?

Here are some high level requirements:

- .Net framework 4
- VB .Net
- Visual Studio 2010 or other dev environment
- Develop a batch of routines to run (I suspect this will be a class)
- Run the above batch as scheduled task on a server
- Run any routine above from a web form (a button for each routine and a progress indicator)

Thanks

EDIT ================

Thanks for the reply, but I'm actually looking for the best design approach and tools for developing a set of routines. These routines will either be run as a batch under a scheduled task or individually by a user via a web form.

This project must be .Net based using VB .Net. Everything else is pretty much wide open to suggestions.

Hopefully, this clears up my question.
Posted
Updated 15-Feb-11 2:38am
v3
Comments
BrettOssman 15-Feb-11 8:28am    
I just found this post which poses a similar question. Answer #1 seems like a good approach, but is that the best approach using the current tools and technologies.

Thanks again.

http://stackoverflow.com/questions/3462371/automating-an-asp-net-web-form
#realJSOP 15-Feb-11 8:47am    
Don't know why this was 1-voted. Compensated.

You could utilize the Windows Scheduler. Here's a VB.NET wrapper library that wraps the Scheduler API:

http://www.mvps.org/emorcillo/en/code/shell/tasksched.shtml[^]

Once you get a hang of the API, you should be able to provide a web interface through which users can configure these tasks.

[Edit]
~~~~~~~~

I went through the link in your comment. The solution you liked suggests using a scheduled console application to do this. The operative word there is "scheduled". What that poster meant is to use the Windows Scheduler. So even if you take that approach, you'd still need to access and use the Scheduler API.

And as to whether it's a good approach, it certainly seems simple to implement and maintain, which automatically makes it a good approach in my opinion.
 
Share this answer
 
v2
When you said "must be VB.Net", you pretty much automatically locked youself into Visual Studio (especially if you want the help resources of millions of developers all over the world). To say it's ubiquitous would be an understatement.

You say it's going to run via a web form, soi I assume this app will be run on the server and not on the client's machine. Is that true?
 
Share this answer
 
Yes, all the routines will be run on the server.
 
Share this answer
 
To sum up the approach in the link I submitted previously:

- Code each routine in a stand-alone VB .Net class
- For the web form interface
- Develop a web form that simply has a buton to run each
routine separately.
- For the scheduled routine
- Develop a web service to execute the routines in the
VB .Net class
- Develop either a Windows Service or Console Application
to execute the web service and schedule it
 
Share this answer
 

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900