Startup Project
-
I wrote and article on VS setup project. http://www.codeproject.com/dotnet/Win_App_Setup_Project.asp[^] It might give you a place to start. Ben
The Express Editions don't come with the Setup projects you use in your article. Express only uses ClickOnce Deployment.
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007 -
The Express Editions don't come with the Setup projects you use in your article. Express only uses ClickOnce Deployment.
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007 -
Neither do I...
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007 -
Neither do I...
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007 -
The results of a quick visit to the Visual Studio Developer Center on MSDN. Look for the Product edition comparison in the navigation tree on the left.
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007 -
The results of a quick visit to the Visual Studio Developer Center on MSDN. Look for the Product edition comparison in the navigation tree on the left.
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007 -
You know it is sort of funny they don't include it. It is not like you don't need to deploy your apps. I guess they just want everyone to start using clickonce. Ben
kubben wrote:
You know it is sort of funny they don't include it. It is not like you don't need to deploy your apps.
The Express Editions weren't meant to build production apps. They're meant to plaay around with so you can get an introduction to the languages they support and the .NET Framework. Those Editions don't even have project templates for Windows Services, Web Services, ..., just Windows Forms.
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007 -
kubben wrote:
You know it is sort of funny they don't include it. It is not like you don't need to deploy your apps.
The Express Editions weren't meant to build production apps. They're meant to plaay around with so you can get an introduction to the languages they support and the .NET Framework. Those Editions don't even have project templates for Windows Services, Web Services, ..., just Windows Forms.
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007Just because they weren't ment to build production apps, doesn't mean it isn't happening. My article is on the windows setup project. I never did one on the web setup. So from my perspective it still make sense since all you have is a windows project. You probably want a way to deploy it. I can understand the windows services not being there. Anyway, I guess it doesn't have to make sense. I am sure somewhere somebody said, "hey look if we leave the windows setup project out of the express version it will save us like half a cent somehow and that adds up you know?" I am sure that nobody is going to buy the full version of VS just so they can get windows setup projects. Ben
-
Just because they weren't ment to build production apps, doesn't mean it isn't happening. My article is on the windows setup project. I never did one on the web setup. So from my perspective it still make sense since all you have is a windows project. You probably want a way to deploy it. I can understand the windows services not being there. Anyway, I guess it doesn't have to make sense. I am sure somewhere somebody said, "hey look if we leave the windows setup project out of the express version it will save us like half a cent somehow and that adds up you know?" I am sure that nobody is going to buy the full version of VS just so they can get windows setup projects. Ben
-
on that note if I write my own setup project template anyone any objections if I post it up on here...
You can put one together, but it doesn't mean that it'll work. The designer support for Setup projects isn't in the Express Editions.
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007 -
Just because they weren't ment to build production apps, doesn't mean it isn't happening. My article is on the windows setup project. I never did one on the web setup. So from my perspective it still make sense since all you have is a windows project. You probably want a way to deploy it. I can understand the windows services not being there. Anyway, I guess it doesn't have to make sense. I am sure somewhere somebody said, "hey look if we leave the windows setup project out of the express version it will save us like half a cent somehow and that adds up you know?" I am sure that nobody is going to buy the full version of VS just so they can get windows setup projects. Ben
kubben wrote:
Just because they weren't ment to build production apps, doesn't mean it isn't happening.
If you use the tool for something that's it's not intended for, is that the tool manufacturers fault?
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007 -
You can put one together, but it doesn't mean that it'll work. The designer support for Setup projects isn't in the Express Editions.
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007hmm, should be able to get something running I would think, I suppose I could just use clickonce for the purpose of the program, it'll work well enough, just means I'll have to rebuild all my datasources, as I'm not a fan of having MDF files in a roaming profile, heh, suppose if I'd set up the SQL properly at the start it'd actually work better as click once...
-
kubben wrote:
Just because they weren't ment to build production apps, doesn't mean it isn't happening.
If you use the tool for something that's it's not intended for, is that the tool manufacturers fault?
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007True, I guess their logic doesn't match my logic in this issue. I guess I tend to try and look at the big picture and do what will help people out in the long run. But I am not so sure that is Microsoft's objective. I am pretty sure they are in the business of making money anyway they can, but that is in part why they are so successful. Ben