Generating Deployment Package For A Application / Structure Takes Project Path?
Mar 18, 2011
I've created a deployment package in visualStudio, the package is generated, but it has an awfull structure, which is basically, the path where I've my project(e.g "CONTENT/D_C/WorkSpace/MyCustomer/TheProjectName/TheDevelopmentBranchFolder/TheCurrentBranch/TheWebApplicationName/obj/Release/Package/PackageTmp/TheSiteIsFinallyHere!!!"
It's problematic, because with the web deployer of IIS, it recreate this path.
So how can I avoid the "D_C/WorkSpace/MyCustomer/TheProjectName/TheDevelopmentBranchFolder/TheCurrentBranch/TheWebApplicationName/obj/Release/Package/PackageTmp" part in visual studio?
Can I create an incremental deployment package using either Visual Studio 2010 Web Deployment Projects or Web Deploy (Web Deployment Tool) .
I need to automatically select changed files from a source and destination or a change set on TFS and build a deployment package only with the changed files.
I am not new to ASP.Net application development but I haven't used some of the new frameworks or features that are used in applications these days.
For cross-cutting concerns, things like: Logging, Caching and DAAB are used in projects these days to implement proven and efficient source code from either Microsoft or other third party vendors such as Log4Net for logging purposes.
I there I have recently created an ASP website wich uses .net 4 and SQL db but soem some reason even displaying 20 records in a gridview is slow... So after some reading I converted the website to a Web Application Project so its compile prior to publish.. But yet again this is a bit slow. pages loading time is not of a bit issue...
Let's say I have a Visual Studio solution with a Web project, a BLL project, and a DAL project. I'm trying to follow the repository pattern keeping my SQL code in the DAL with an interface that is referenced by the BLL.
I have a handful of common solutions for things such as error handling, usage logging, and other things that can be considered utility functions (i.e. not in the business spec). I'm keeping these in a Common project.
Here are a few ideas I've had with regards to structuring the Common project...
Bundle SQL with logic in a given class
Create a layered solution within the Common project
Discard the Common project and put utility functions in with BLL/DAL
Is one of these ideas better/worse than the other? Does anyone have a better solution?
It's worth noting that these utility functions will be reused in a variety of other applications.
Im trying to build a deployment package out of VS2010 against a web project and want to include all IIS settings as configured in IIS Manager. However when i enable this i get the following error message
Object of type 'manifest' and path
[code]...
Now this error makes very little sense as the specified application does exist in Default Web Site. I've checked the spelling. I've tried having ISV as a virtual directory and as an Application and tried with and without the ISV folder.
On the Web page i hae the Project URL set to [URL] On the Package/Publish tab IIS web site name is set to "Default Web Site/ISV/Web.Crm.Framework/"
Bing/Google search turn up very little on this and the documentation is not really detailed enough.
I already published my client's site and i received problem during loading page.
here's the error.
Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.
Compiler Error Message: CS1501: No overload for method 'UpdateBookInfo' takes '5' arguments
Source Error:
Line 33: //Update Book Info Line 34: Book BookProcess = new Book(); Line 35: BookProcess.UpdateBookInfo(SKU, Title, Description, Price, Status); Line 36: Line 37: //Update Book Picture
I don't understand how to use this feature called "Build deployment package" in VS 2010. I go to my properties and go to package/publish web and setup it up. I click "Create deployment package as zip"
I then build the deployment package and get a zip file.
When I look into and start drilling down in the folders I find I get a path like this
[Code]....
I don't understand why it makes all these folders and on top of it why is it my path to where my soultion sits. I don't like the fact that now everyone can look in the zip and see my accoutn name, where the file was sitting, that I am using subversion.
Then it makes it so confusing to when a error happens. I deployed it on my IIS windows 2008 server and ran it and I had a error show up. It pointed to the file where the error occured and the path was point to my desktop.For the longest time I could not understand why it was pointing to my windows 7 machine desktop when it was running on a windows 2008 server located in a different country.
It was not until I found out with the zip path it made sense. But that is confusing when it is pointing to paths that don't exist on that computer.
I have an asp.net app in visual studio and it's starting to contain quite a few files. I remenber seeing a .sln file format that converts the entire files into one file. How does this work?
I am having a silly beginners problem with ASP.Net/Visual Studio 2010. I would like to integrate a number of third party packages into my asp.net MVC app (e.g. CKEditor, TinyMCE.) During the prepwork I sooner or later end with instructions to the order of "copy the package into your project/scripts directory". Sounds easy but I still can't figure out how to do it.
For the time being I trick visual studio into adding the package by adding a blank directory, then go to windows exporer to copy files into the directory, then go back to visual studio to add them one by one. That works for a few javascripts but not for a more complex package. Clearly there must be a better way to add a third-party hierarchical structure to a project, right?
I want to structure my ASP.NET MVC 2 web application sensibly using Areas. The application consists of the two main parts Website which is the default part and Dashboard which administrates the site using a CMS. (Probably, more Areas will follow later on.)
How do I structure my project best? Should I ...
create the Area Dashboard and put the stuff belonging to the Website part into the main application folder or should I create both Areas Website and Dashboard?
Additionally, where should I place my Entity Data Model and the corresponding Repository classes that have to be accessed by both Areas?
I am using asp.net 3.5 and I am trying to create a project structure (asp.net web solution with UI/Business/Data access) which would be like a base and ready for any new projects in my team and all could use this standard structure only as a base(outer boundary) and they can expand the structure. Also adding on to it I wanted to include certain features like adding libraries of reusable code/functions, so that every team member could use functions from my library within this base structure. To summarize the above, I need to create standard .net project structure/framework/architecture with resusable code library included in it. How can I do this..
I am developing an ASP.Net web application for my client which is into Multi Level Marketing Business. I need to show him the treeview of the members under any member he chooses. For eg. he selects 'Member A' from the DropDownList, and clicks Submit, he should get a treeview of all the members under 'Member A'
I need to deploy 3 projects using one single installer. The first project is a web project the second and third project are windows services.I need to use the .Net Deployment project to deploy all the project is a single installer. I have managed to create a installer and a custom action which gets the primary output of the both windows service but I am having problems installing the Web application.
If I create an output for the web application it gets installed in the application's folder and not on IIS folder and its not set as an application.
I built the solution once in release mode and it created all the necessary files in the release folder. I then deleted all the contents of the release folder. Now when I buid it for the second time, the release folder is empty. The dll is in the debug folder.
I need to obfuscate a dll that is used in a ASP.NET project, the deployment project pruduces a setup.exe which I want to distribute. I have the VS 2008 Dotfuscator installed but when I build the deployment project the project that creates the dll is rebuilt before it is added to the deployment project and added to the setup.exe.
My web application functions as expected when using non-compiled web pages. When I used a Web Deployment Project to build my solution (creating a separate assembly for each page and control output), the web application does not function (e.g.: pushing a button does not result in any action).
I am trying to deploy an ASP.NET 3.5 Web Application to my production server and I am using the Web Deployment Project for this purpose. I have a folder named MasterPages in the root of the application which contains all the master page files. When I build this project in the release mode and deploy it on to the server I am getting the below error message:
Directory 'C:inetpubwwwrootMasterPages' does not exist. Failed to start monitoring file changes.
I am using ASP.NET AJAX and the ToolkitScriptManager is on the master pages. I have noticed that the MasterPages folder is missing from the release build.
I have a jar file exporting some functions which i want to use in my asp.net application. How can i achieve this? Will anything change if i use it in an windows azure application?
Have been searching for a while but am having no luck fixing this. I am running VS 2010 on a Win XP machine. My agency's developer converted our web app with no problem, and i can open it and compile the code in VS 2010. I am trying to run my wdproj to build the site to a local directory, and it will not. I get an output error:
Error 2 Unrecognized attribute 'targetFramework'. Note that attribute names are case-sensitive. C:Ronweb_sitesTESTDEVpctweb.config 76 1 pct.deploy
I have a project which involves a database (sql server 2008 express) class library, webservice and a website which I want to deploy on a windows server 2003 with IIS 6. I look ed on the web and how to do this for the website mostly but unfortunately not that much for the webservice, classlibrary and database.
According to this website, I can go to Visual Studio 2005 Web Deployment Projects, and download the add-in, but I am not finding what I need. I have searched other sites for the add-in as well, but with no luck. where I can download the add-in?
If not, can someone provide documentation on how to properly deploy an ASP Web application? I have tried on my own, but I am apparently doing something incorrectly or incompletely, as I have several different problems with my current deployment. So I am looking to start over with the help of this add-in or by following more detailed documentation.
Is there a difference between the Web Setup Project in VS2008 and the Web Deployment Project that I keep reading about on this site? More importantly, how much of a help is the deployment project over just using the setup project?
