I'll throw in my two cents here. Not to insult you, but I think you are choosing the wrong 'path'. In my opinion there are only two cases where you may consider choosing not to go for the assembly task when you code in .NET. The first case is if you have a type of problem that needs a solution that will not be needed again, and the method is really small (even then I would consider an assembly). The second case is if speed is critical, for example in a loop (loading assemblies can take from milliseconds to several seconds in VC).
The advantages of of using assemblies compared to the .NET tasks are loads, but I'll mention a few here:
1) You get access to third party libraries that you won't have in the .NET task
2) You have an easy way of keeping your libraries up to date through NuGet.
3)You can code 'the proper way' using classes, interfaces, repositories, dependency injection, unit testing. You name it.
4)It will be a lot easier for the next developer to inherit your code.
5)You can get the help from tools like for example Resharper to write better code.
And a million other reasons. The best part is that it's easier to deploy to your visual cron server, than copying and pasting code. You can just 'publish' you code to a particular folder on the server, and job done. If you should need to move the code (dll) further, to say C:\ on the server, you can create a VC job that copies the files.
Don't create loads of .NET tasks instead of an assembly. You will regret it.
Thomas