Visual Studio :: Build For X64 Using VisualWebDeveloper2010Express?
Dec 28, 2010
I Built my project for x64 Using VisualWebDeveloper2010Express.And I tryed to execute it in Win.2003 x64 environment, it did not run..Net Framework 64 and IIS were installed in win.2003 x64.
I have a question regarding a situation that occurs with GridView, ObjectDataSource in ASP .NET application. The GridView is linked to the ObjectDataSource and both are included within an UpdatePanel letting the GridView to fill in an asynchronous way from a form in the same page so it gets more rows as the user enters the data:
I start the project with Visual Studio 2008, fill the form and it works correctly. Then I stop the execution: rerun again and the data I entered in the previous run is in the GridView. Is like some sort of cache saved the data from the session before. I checked that EnableCaching property is set to false for the ObjectDataSource. If I Rebuild Web Site in Visual Studio (not just Build) then it works corretly leaving the GridView empty. Is this caused just becuase of Visual Studio? Can it be turned off? And will it happen in the final IIS it will run on?
I really like the new transformation feature for the web.config. It seems to work when I do "Build deployment package" but not when I just want to locally start the debugging using the green arrow. It just uses the web.config without processing theWeb.Debug.config. I can prove that because in web.config I have debug="false" with a transformation in Web.Debug.config so that it gets true but everytime VS asks if it should modify the web.config to enable debugging which it should've done automatically with the following transformation:
[Code]....
Am I missing something here? I used to work with NAnt to modify/create the web.config as a pre-build event but I thought that I wouldn't need it anymore. Am I wrong? The project is a freshly created asp.net mvc 2 web application.
When working with an ASP.Net application, when I rebuild the solution, I would like it to automatically refresh the current version thats running through the integrated server in the browser.
I have looked through post build commands and afterbuild targeting but I have not been successful so far. I would like to do this straight through VS2008 if possible without needing to install anything extra, put if thats not possible then any solution would do!
So here is the problem, when I build my web application in Win 7 x64 and publish (copy) to 2008 Server R2 (also 64 bit), the application won't run when I navigate to a page that uses a 32 bit dll.
When I boot to the Vista x86 partition and build and publish (copy), same code, minimally modified sln file to redirect to same code location. I've created a new entry usiong Menu > Build > Configuration Manager and created a x86 entry. I thought that was all I needed to do to force VS to build to a 32 bit machine. Am I missing something or do I just need to boot Vista when I want to work on my web site?
i m using VSS 2005 and VS 2005. on one machine i installed VSS 2005 and create project. on second machine i opended my project using project source safe, it ask me for user detail and i enter details. i got the complete project. problem is that when i try to run project i got following error. "An editor or project is attempting to check out a file that is modified in memory, which will result in saving it. Saving files during the build process is dangerous and can result in incorrect build outputs in future. Do you want to continue with the check out?"
I've got a solution that contains several projects. There is a main exe project which I'll call MyProj.exe that references several other projects which reference yet other projects in the solution. Additionally a few projects in the solution are not in MyProj's reference chain and aren't regularly built. There is 1 project (a class library project) named Payment which is giving me a particularly hard time. The two of MyProj's references have a project reference to Payment.dll. So the reference heirarchy looks like this:
When I right click MyProj in the Solution Explorer and choose Build, everything works fine, but when I choose Rebuild, I get the following results:
Payment.dll is deleted but never rebuilt. It doesn't exist in the output directory MyProj.manifest in the output directory doesn't have a reference to Payment.dll. (What is this file? I don't remember normally seeing it in other project's the output directories.) 19 of the project .pdb files are deleted and not rebuilt This is a big problem for me because this is a ClickOnce application and when I'm publishing, Payment.dll isn't getting included in my deployment which is a problem I suspect is closely related.
I want to write a class using c# and compile it and user this dll in many projects.
I know how to build a website in Visual Studio and publish it but Visual Studio mixes the classes and rename them to a few strang and unfamiliar names which doesn't mean anything.So my purpose is writting a class with some functions, compling them and use them in other projects.
How do I build a web application project from command line using Web Developer Express 2010?
I am using the same command format that I would use with devenv.exe (Visual Studio), so I can evaluate us moving forward to VS2010. However, I am having real trouble building our code. Our solution consists of 4-5 projects, consisting of assemblies. The last assembly is the web site code. The root .sln file is the one which when opening in the IDE can click Rebuild All, and the DLL's of each project are generated and then brought into the website project.
However, when I run vwdexpress.exe from the command line nothing happens and no Dlls are generated. This is not giving me any confidence to run with VS2010.
The in folders of each respective project are empty, but it takes 3-4 seconds for the command to finish, which gives me the impression it did something.
Basically it's in the title. There's a bug in a VS2003 website that needs to be fixed but it is not letting us rebuild the entire project and the bug needs to be fixed immediately. Is it possible to only rebuild the dll that has the bug in it, transfer it to the server that's hosting the website and have it work?
Create a control 'ClassName' in file ClassName.cs. Path is c:ProjectWebuserControlsControlTypeClassName.cs
[code]...
The really bizarre thing is that the error is inconsistent.Sometimes the project builds, sometimes some files break the build, sometimes others do, sometimes all of them do.
I had no problem with this in Visual Studio 2008 but it seems that VS 2010 is having an issue, and I'm betting it's probably me.I have a solution with an ASP.NET Web Site Project and a few C# projects (BLL, DAL, Tests in NUnit). I have configured the build process for the test project to automatically run NUnit to run the tests. I would like to ensure that the BLL and DAL projects build before the test project so that the tests will run against the latest compiled version (yes, I know I could do this all in one project, but I'm choosing not to -- please bear with me :) )
So, I set the dependencies of the Test project to include the BLL, DAL, and Web Application projects, and the build order shows BLL, DAL, Web Application, and then Tests. However, I noticed that the BLL doesn't actually build when I build the Test project.Any idea what this could be or any option I might be missing to force the other projects to build when I build the Test project?
I'd like to add build configuration dependant web config files to my empty ASP.NET 4 Web site project. How can I do that? According to this blog entry, VS 2010 is supposed to provide a context menu entry on the original web.config file, Add Config Transform, allowing to add build configuration dependant web.config files to the project. But this context menu entry doesn't exist. What did I do wrong?
Steps to reproduce:
Create an empty ASP.NET 4 Web site project on localhost (IIS)
I am currently attempting to use Visual Studio 2010 'Publish' and MSDeploy functionality to handle my web deployment needs but have run into a roadblock with regards to customizing the package depending on my build configuration.
I develop in a 32bit environment but need to create a release package for a 64bit environment, so in the 'Release' configuration I have a post build event that copies the 64bit version of a third-party dll into the bin directory overwriting the 32bit version. When I use the 'Publish' functionality, even though the correct 64bit dll is being copied to the bin directory, it doesn't get included in the package.
Is there a way to get the 'Publish' to include files that have been copied into the bin directory during a post build event?
I just used the wonderful tool Microsoft Ajax Minifier and it's working very well when I build my MVC application on my machine but when I check-in in source control and started build by the Team Build 2010 it doesn't create the min files, for sure I can't put the mini files inside the source control as the recommendation from the Microsoft Ajax Minifier because it's like the dll it's generated every time you build your application so no need to put it in source control beside it can't be because you will need always to check-out this file to build and this will prevent other from build using the team build, so what I need to do to make generate the mini file with team build 2010?
When I'm building my web project it takes about 20 seconds to compile. Then when I try to browse to a web page in project, asp.net does its runtime compilation(another 20 seconds). I know I can't escape these steps because thats how asp.net works, just want to see if anyone has some kind of optimization to make these builds faster.
I got a project when after opening in visual studio 2005 in build mode drop down, only debug mode is shown but release mode not shown.Project builds successfully in debug mode is there a way to enable release mode.
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.