Bill Crawley
August 31st, 2005, 09:50 AM
Hi All,
I have just written my first asp.net solution and I now need to deploy it. As part of the solution I also wrote an asp.Net Control in C#/Javascript. I didn't take any notice of this property until now. I am having difficulty trying to work out what is going on under the hood with this property.
I went back to my control and changed the Build Action to Embedded Resource, because I felt that's what it really is in my main project. In my main project I have left this property on all forms/classes as their default. I have set the solution config to release.
I'm hoping this is enough when it comes to deploying, I understand that depending on how I deploy I may deploy only those files needed to run, all files etc. But that the files that are deployed in each of the scenarios are dependant on the value in the Build Action Property.
I would be grateful, if someone could explain the differences and what is going on under the hood with this property.
I have just written my first asp.net solution and I now need to deploy it. As part of the solution I also wrote an asp.Net Control in C#/Javascript. I didn't take any notice of this property until now. I am having difficulty trying to work out what is going on under the hood with this property.
I went back to my control and changed the Build Action to Embedded Resource, because I felt that's what it really is in my main project. In my main project I have left this property on all forms/classes as their default. I have set the solution config to release.
I'm hoping this is enough when it comes to deploying, I understand that depending on how I deploy I may deploy only those files needed to run, all files etc. But that the files that are deployed in each of the scenarios are dependant on the value in the Build Action Property.
I would be grateful, if someone could explain the differences and what is going on under the hood with this property.