aah stupid me:D so far I have only 2 sections, a journal section and a section for an aim profile. Assuming WebApplication2 will be my whole website, do you think this looks right? :
http://vbforums.com/attachment.php?postid=1481845
should I do this? or should I make separate projects for each section? (ie a separate project for journal, a separate one for aim?)
Thats fine. Make sure you use user controls. Also you might want to change those vb extension to cs :D j/k
Ya, for such a small site, it is fine. If you are going to be developing them into much bigger sites, you may want to go ahead and split them....and also split the shared files they use into different projects.
I also agree that you should switch over to .cs files... :)
I gotta agree with the rest of them. 2 things.
1. Change the file extension to .cs
2. Get a new web application name ;)
Long live .vb!!!!
:D
LMAO!!!!!!! :p
I dont think I'll ever give up VB. Some things are just easier in VB than C#. Writing code for Office 2003 in C# is a pain in the ass, so I'll be using VB.NET exclusively for Word 2003 and Excel 2003 programming.Quote:
Originally posted by Edneeis
Long live .vb!!!!
:D
Just out of curiosity, what's makes it more difficult programming Office in C#?
hehe ok, yeah and long live VB... umm well this is actually the second project I've ever made, so let it be WebApplication2, it has a really cool name :D :p
umm so what's the benefit of making separate projects (if I add more pages I may split it as you guys said)?
I've noticed that it takes a long time to load a page for the first time after it is compiled. So if I have 20 pages in a project, I edit one of them only and then I compile the project, does it actually recompile every page? ( I dont even know how does this compile thingie works :D) would all the pages slow down again on their first view?
umm and also besides the first time viewing of a page, is there any performance difference in having multiple projects vs. having everything in a single project?
That would be one benefit to breaking down the projects into seperate ones. If you change a file in one project and compile it, it will only affect that one project, the other can keep on going with no slow down.Quote:
Originally posted by MrPolite
hehe ok, yeah and long live VB... umm well this is actually the second project I've ever made, so let it be WebApplication2, it has a really cool name :D :p
umm so what's the benefit of making separate projects (if I add more pages I may split it as you guys said)?
I've noticed that it takes a long time to load a page for the first time after it is compiled. So if I have 20 pages in a project, I edit one of them only and then I compile the project, does it actually recompile every page? ( I dont even know how does this compile thingie works :D) would all the pages slow down again on their first view?
umm and also besides the first time viewing of a page, is there any performance difference in having multiple projects vs. having everything in a single project?
Performance wise, you shouldn't see a big difference breaking them down into multiple projects. Maybe the calls to seperate dll's will take a tad longer, but not by much, especially since you reference them in the project itself. The biggest thing you get is that you have a more managable project structure. If you have two different applications doing two different things, the should be seperate. Easier to maintain when they get bigger.
if i am not wrong as C# doesnt allow late binding you cant use it without reflection against vb which allows late binding:rolleyes:Quote:
Originally posted by Lethal
Just out of curiosity, what's makes it more difficult programming Office in C#?
Its not difficult, its just tedious.Quote:
Originally posted by Lethal
Just out of curiosity, what's makes it more difficult programming Office in C#?
C# does not support optional parameters and alot of the functions in Word or Excel allow as many as thirty or more optional parameters. So if you call a method in Word that requires 30 parameters, you have keep putting Type.Missing for the parameters that you dont want to include. VB.NET supports optional parameters so its much easier.
Also in Word parameters must be must be passed by reference and you can only pass lvalues. So if you want to pass 30 parameters, you have to declare 30 object parameters, assign what you want to them then pass them by reference. Doing all this will drive me nuts. So I'll be using VB.NET for Office programming. At least I'll have some hair on my head when I'm done :D .
hmm i think i made mistake with VS.NET scripting or something like that that could be only be done in vb.net :confused: