I have a project where I need different versions of the same site.
I need to accomplish this by having different versions of the same resource files.
I would like to store the different versions of the same resource files in seperate projects in the same solution. Then choose which project of resource files to use when I publish or compile.
I've been searching the net everywhere and my deadline is coming up.
I have a project at work where I need different versions of the same site.
I need to accomplish this by having different versions of the same resource files.
I would like to store the different versions of the same resource files in seperate projects in the same solution. Then choose which project of resource files to use when I publish or compile.
I've been searching the net everywhere and my deadline is coming up.
I have a project at work where I need different versions of the same site.
I need to accomplish this by having different versions of the same resource files.
I would like to store the different versions of the same resource files in seperate projects in the same solution. Then choose which project of resource files to use when I publish or compile.
I've been searching the net everywhere and my deadline is coming up.
We have been building ASP.Net websites for many years. During this time we gathered a lot of knowledge of ASP.Net. We know what to use, a what not. One problem is still, persistently, bugging us. I hope to solve this for once and for all.
We have a fairly large solution with lots of aspx-files. All aspx-files reside in one Web Application Project. This single big WAP needs to be split in multiple smaller projects.
There are a number of ways to accomplish this, but I am still unsure what the best way would be. We use ASP.Net 4.0 and Visual Studio 2010 Premium.
This is our current work-around (which we do not like)
[code]....
i have two projects in one solution...
project A
project B
in project A i have page in--->Home/Account(page)
what link i have to use from project B to open the page in project A
I'm totally new to the Microsoft dev scene so please go easy :)Currently, I have a solution that contains two projects (ASP.net websites, FWIW). If I create a class in Project1, how do I expose it to Project2? Is it automatically available to Project2 because they are in the same solution? Or do I need to do something special to make the connection?
View 5 RepliesI am looking for general direction on the best practice here. I have a class that I want to share between two different forms in two projects that are associated. The two forms are in seperate projects but both projects load together as I have added the second project to the first. I also have a class that I want to share between these two projects which will cause me to add another project to this solution with will mean I will have three projects in my solution. My question is how do I best share this class?
I believe the only way to do this is to add the class in the reference in both of the form projects?... Is this correct ? I'd really like to just reference the class and inherit it in the source code without adding it as a reference but I am feeling that I can't do that. I am obviously pressed for time and working on other projects and a I am a experienced coder with only about 1 year of C# experience...
I am attempting to setup Config Transforms on my project that I migrated to VS 2010. The web project works just fine, but I have a WCF Host project that I seem to be unable to add transforms.
Has anyone had this problem before?
If MVC application has multiple projects (The solution may grow large in future). These projects may share controllers such as application controller accouts controller and there may also be a situation in which namespace of one project is shared by other project. What is the best way of implementing such solution. One approach may be to use areas.
View 4 RepliesInitially, in my solution I had one project, and had set up all that is required for asp.net security, and that includes users and roles and access rules, etc. All of that was and still is working fine.
Now I added another project to my solution, and my first project points to pages in the second project.
The problem is that it seems like the users and roles are not being transferred accross projects. Not sure if I am explaining my problem correctly...if not, feel free to ask...
Its my first time trying to manage users and roles accross projects within a solution.
I am currently extending the NopCommerce solution for a client and have some general questions about workflow, since this is a relatively large solution for me (50+ projects).
I want to add some classes to the DAL, BLL, and so forth.
What would be the recommended process for this workflow? For example, I created a class in the DAL -> ran build. Then I created a test.aspx page in the main project which instantiates this class -> ran build; however, adding just one line of code causes the solution to rebuild all other projects such as payment modules, which makes the process tedious.
Am I approaching this in the correct manner? I have read about: creating a seperate solution with relevant projects; is this the recommended approach?
In our web application we need to keep various company's settings. For eg "DiamondProdRefIDCaption","Shippingpickup","ZipCodeCaption","DefaultCountry","AllowToEditInvoice", etcThese settings are different for various companies and are placed in web.config as key-value pair.Initially, we have tried do simplify this process by adding a company_settings table in the DB so as to allow us to add companies on the fly. However, this method makes it very difficult to add a new setting
<%$Resources:DiamondProdRefIDCaption%>
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 am using VS2005 and I have a solution file (.SLN) which has 8 projects. I moved the solution file to a different path on a shared folder to have better organization of my projects and to allow access to the solution/projects from any computer on the network. After that, I edited the .SLN file so that the path of the projects in the solution file are correct (all on shared folders).
After that, I opened the .SLN and everything seemd to be working fine. However, I notcied that the "Start Options" of the website part of the solution file is missing the "Start Options", ie, the Start Options are reset to default values. I think also, but not sure, some other settings of the Solution/Projects have been reset.
Questions:
1. Where the Web Site "Start Options" are stored ?
2. How I can maintain the Start Options and similar settings if the .SLN file is moved or opened from different computers on the network ?
3. I am not using an team development tools, only plain (vanilla) VS 2005 Prof. Edition. Is it possible to have 2 or more developers work on the same solution/projects (shared on the network), if both developers will coordinate manually simultanous access to the porject files/resources/source code ?
Using ASP.NET v3.5 / VS2008.
Is there a way to share class files across web site projects without actually making a physical copy of the file to the App_Code folder of each project?
I am trying to add multiple CSS files across several projects and have added them as a "link" but when I build my solution it does not copy the files. Is there any way to share a bunch of CSS files across several projects?
View 7 RepliesI have a solution that I pasted some files into. The files that were pasted into it won't show up in the solution explorer. These files are for a tutorial from MSDN. The files were pasted into the folder that contains the solution using the file system.I then refreshed the solution explorer to include the files. I've done this before with out issue. For some reason it won't work this time. When I did this before I pasted the files into the folder that holds the solution, refreshed the solution explorer and then had to include the files into the project and all was good.
View 4 RepliesI have a web application that has some non-web projects as well. When using Web Deployment, a single assembly is generated for all the aspx.vb files. When using Team Build (TS 2008), a lot number App_Web_xxx.dll file(s) are generated instead of a single assembly. How can i solve this problem and change the TFSBuild.proj file so that it can generate a single Web Assembly instead of a lot number of assemblies.
I guess thats because the MERGE operation is not occurring like it used to happen for Web Deployment Project in my solution. How can i enable MERGE of App_web_*.dll files into a single Web.dll assembly file and delete the satellite assemblies? Here is my code from TFSBuild.proj file: (MY web project is in Release|.NET Config and all other projects within the solution are in Release|Any CPU)
<Target Name="AfterBuild">
<PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug|.NET' ">
<DebugSymbols>true</DebugSymbols>
<OutputPath>.Debug</OutputPath>
<EnableUpdateable>true</EnableUpdateable>
<UseMerge>true</UseMerge>
<SingleAssemblyName>Web</SingleAssemblyName>
<DeleteAppCodeCompiledFiles>true</DeleteAppCodeCompiledFiles>
</PropertyGroup>
<PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Release|.NET' ">
<DebugSymbols>false</DebugSymbols>
<OutputPath>.Release</OutputPath>
<EnableUpdateable>true</EnableUpdateable>
<UseMerge>true</UseMerge>
<SingleAssemblyName>Web</SingleAssemblyName>
<DeleteAppCodeCompiledFiles>true</DeleteAppCodeCompiledFiles>
</PropertyGroup>
</Target>
We have a web portal product from which we customize portals from customers. We use the precompiled web app and create a virtual directory (vd) where the customization resides. In addition to this we do some changes web.config in the web app folder. We would obviously like to keep these customizations under TFS source control.
When I try to add the precompiled web app (which I don't want to add to source control), a warning tells me that the vds cannot be added. If I only add the folder that is referenced to by the vd, I lose the references to assemblies in the precompiled web app.
My questions are:
How do I structure a solution for adding IIS (sub application level) virtual directories and still retain the references to assemblies? Is it possible to add other directories/files from the web application level (like App_Theme, web.config etc.) to the solution?
Since we already use Visual Source Safe, we have established a tree structure for each customization project:
Project Root
|
|-Custom Sql
|
|-Custom Portal Files (which is added as a virtual directory)
|
|-Other Customizations
I could probably do a lot of this manually through the source control explorer, but I'd like to have everything done through a solution.
I've followed the instructions using this article: [URL], but this doesn't address the exact problem that I have. Oh, and we are currently using Visual Source Safe for portal customizaton, but are eager to make the move to TFS.
I have multiple projects that need to share resource files (.resx) Suggestions have been made to move resource files to a separate assembly and have web projects reference it. Is there an example of how to do this?
Do I create a new Class Library project and move App_GlobalResource folder inside of that? I don't think that will work because code classes that are generated for resource files are marked as 'internal' which means that they can not be accessed outside of this assembly.
I have a website which currently uses EN-US and I also have resource file for french. what code should I need to write to make the application use the french version of the resource file.
The site is a commerce server and share point site that uses .NET
I have a multilanguage application and I use resource files (.resx). I hired a person to make the translation. My question is, am I supposed to give him the resource files in order to make the translation and how he will open the resource files? Obviously, he doesn't have a copy of Visual Studio! Is there any tool that I can give him in order to work with the resource files?
View 2 Repliesthe website i'm working on has resource files for a number of languages.The resources of the website are compiled in the website dll (i think?) and the resources from other, from the website, referenced dll's, are stored in subfolders of the in directory.So i have in the bin my website.dll, and a subfolder called es with the Spanish resources for the website.services project (called website.services.resources.dll) and so on.Now we have the site live, and there is a wish for a immediate change of one of the items in a resource file.As my .resx files are compiled, i have to change the resource in the dll.
View 2 RepliesFor some reason I have a solution with a single project and the solution files are in the same directory as the project is. I consider this ugly and want to change it by moving the solution files in a superordinate directory.
For now I have edited a single line in the .sln file:
Project("{FAE04EC0-AAAA-AAAA-AAAA-00C04F79EFBC}") = "projectname", "projectname.csproj", "{5D5A753D-AAAA-AAAA-AAAA-C535851E8DC8}"
changed to
Project("{FAE04EC0-AAAA-AAAA-AAAA-00C04F79EFBC}") = "projectname", "directoryname/projectname.csproj", "{5D5A753D-AAAA-AAAA-AAAA-C535851E8DC8}"
It seems to work.
Could this have been all I needed to change? I have the feeling that I missed something.
In my company app we have organized it something like the following:
1. Solution (Transcripts)
Solution Folder - Lib
Solution Folder - Debug
Solution Folder - Release
Class Library Project
Web Project
My Question:
1. All my references from Web Project are referencing to the DLL's in the Lib folder under Solution (Transcripts). Why can't we refere to DLL's directly under Web Project why the need of creating a new solution folder "Lib"?
2. When we publish the Web Project. Does that mean that all the DLL's under Lib solution folder also gets published?