Normally the edmx and other related entity framework files are embeded in the dll.
For our current project we would like to have them external to the dll in order to change the prefixes between environments.
Is there a way to tell Visual Studio not to embed the edmx files?
For example:
DEV.Table1 in development
PROD.Table1 in production
If this info in in the dll, we cannot copy the dll's between environments and just change the info in web.config.
Yes you can use external EDMX file. As alternative you can also check Model adapter to support these changes without needs for external EDMX.
Related
i need to port a VS2005 Project (.NET2) to a VS2008 (.NET3.5) (or to VS2010 .NET4 not yet defined).
The project is composed by:
resources and configuration files (VS project files, like: .settings
.vbproj .myapp .config .xconfig .Designer.vb);
a lot of VB codes;
xsc, xsd, xss and xsx files;
a lot of Crystal reports for VS2005;
graphical resources.
The application take data in order to generate reports from more DB SQL Server 2005 istances.
What is the best way to approach to a migration activity?
Is there an internal migration tool?
If yes, what's the best practice to use it?
Which kind of files will be automatically ported to the new VS version?
Thanks in advance for all the provided information
It should be backward compatible.
Therefore, you should be able to simply open the project in the target version of Visual Studio and perform a conversion if required (for the project files). I suggest taking a backup first however, just in case.
Then compile test and test some more.
Should be fine.
I am using Visual Studio 2012 to create a class library project that will also include a number of TypeScript (.ts) files, as well as their generated .js and .js.map files. All of these files need to be included in the assembly as embedded resources, so that they can be exposed to a consuming ASP.NET MVC application via a custom VirtualPathProvider.
Note: although only the generated JavaScript files are essential for the production environment, the .ts and .js.map files must also be accessible to the web application, for debugging.
This presents a conflict, since TypeScript files are usually assigned the TypeScriptCompile build action but I also need them to be assigned EmbeddedResource.
Is there any way to assign multiple build actions to a VisualStudio project component? Alternatively, is there another way to get TypeScript to compile files that are not explicitly marked as TypeScriptCompile or to get Visual Studio to embed files that are not marked as EmbeddedResource?
Thanks for your suggestions,
Tim
If you had a TypeScript file that referenced all of the others, only it would need to have the TypeScriptCompile type as the compiler should walk all the dependencies and compile all the rest too.
So creating a file that acts as the compilation target and that references all of your other files might allow you to change all the rest to EmbeddedResource.
I created a new file-system based web site in Visual Studio 2010. On property pages I've set to use .NET 4.0, but I cannot find System.Windows in the Add Reference dialog. The only copy on my PC seems to be in this directory, but this is not a Silverlight project
C:\Program Files\Reference Assemblies\Microsoft\Framework\Silverlight\v4.0
I thought it might have something to do with the client profile vs full version, but I can't see where to specify that in a web site project.
What am I doing wrong?
Not all namespaces have corresponding DLL file names used in the Add Reference dialog. System.Windows is one of these.
For example, System.Windows.Clipboard is resident in the PresentationCore.dll, but System.Windows.SizeConverter is in WindowsBase.dll. It all depends on the actual types you need to access.
System.Windows is the WPF base classes - you cant add that assembly to an ASP.NET site. You will need to change your application type to use it.
I've generated pseudo-localized versions of an app's resource files (for example Order Summary and Payment is localized as [[[[[Òŕd̂ër̊ S̀úm̂m̈år̀ý ân̈d̊ P̀áŷm̈e̊ǹt́]]]]]) so that we can test for localizability bugs ahead of getting actual translations.
I have named them using the qps-ploc resource identifier to match the existing pseudo-locale identifier, e.g. my pseudo-localized version of Details.resx is named Details.qps-ploc.resx.
However when I add these resx files to the project, Visual Studio ignores them. If I rename them using a "real" language code (such as Details.fr-FR.resx) then Visual Studio does create a subfolder named with this language code and builds the satellite assembly.
So it looks to me like Visual Studio rejects qps-ploc (without even a build warning). Am I missing something or can anyone suggest a way to get these qps-ploc resources built as part of my Visual Studio project?
The qps- locales work fine in my ASP.NET web application with .resx files (not compiled resource dll), however, I did find this MS article on enabling pseudo locales in the registry. Perhaps it will help.
Using Pseudo-Locales for Localization Testing
Additionally, you may wish to create custom locales, as given in this MS article:
How to: Create Custom Cultures
Best regards.
When I use external library like Spring.Net, NUnit, NLog and etc. I don't see documentation for public methods (intelisense). How can I fix it?
You need the .xml file that contains the IntelliSense info for the assembly. Make sure it is stored in the same directory as the reference assembly for these libraries, it has the same name as the assembly but with the .xml filename extension. Maybe you forgot to copy it or cleaned-up too aggressively?