project-reference

Resolving incorrect project reference GUIDs

由 喜欢而已 提交于 2019-12-21 15:19:30
问题 I have some projects in a Visual Studio solution that have ended up with project references that include the wrong GUID for the referenced project. (Possibly due to the referenced project being recreated at some stage) eg. Consider a project CoreProject.csproj with the following properties: <ProjectGuid>{93803F9C-8C65-4949-8D44-AB7A3D0452C8}</ProjectGuid> <OutputType>Library</OutputType> <RootNamespace>CoreProject</RootNamespace> <AssemblyName>CoreProject</AssemblyName> Another project

VS2010: Warning on add project reference to Silverlight project from .NET project

由 北城余情 提交于 2019-12-18 12:26:05
问题 In VS2010, Silverlight 4, .NET 4, I've got a WCF service and a Silverlight app, and Silverlight is accessing the class not with Add Service Reference but by sharing the contract. Naturally, this means I have the contract in a Silverlight class library, and the service has a project reference to that library. Strangely, this results in a /!\ icon on the reference, and a warning: The project 'SilverlightClassLibrary1' cannot be referenced. The referenced project is targeted to a different

Reference trouble with BizTalk schema project in Visual Studio 2008

由 时光毁灭记忆、已成空白 提交于 2019-12-13 14:29:34
问题 In a large VS 2008 solution we have different schema projects and mapping projects. The mapping projects reference the appropriate schema projects and this works fine overall. However, recently I added a new schema project and it consistently gives the same problem. When I add a new schema to it, and I want to use that schema in a mapping project that already has a reference to the schema project, the map fails to validate with the message Cannot load source/destination schema [...]. Either

Difference between project and dll dependencies in .Net in the final compiled assembly

由 ∥☆過路亽．° 提交于 2019-12-12 08:45:28
问题 Lets say I have two projects A and B. A depends on B. I can specify this in two ways: Include A and B in the same solution and specify B as a project dependency for A. This shows up in A's msbuild project as a "ProjectReference" node. Include a reference to the B's compiled dll as dependency for A. This shows up in A's msbuild project as a "Reference" node My question is, once I've build the assembly for A, is there a difference in the final output between these two methods. I tried creating

Reference from assembly to DLL in Visual Studio solution

由 烂漫一生 提交于 2019-12-12 05:29:21
问题 Say, that we have .NET application App along with additional assembly ClassLibrary , which, in turn, uses native DLL called Library . All these are in single solution, so I may set up the dependencies etc. The catch is, that I want the Library to be automatically "attached" to ClassLibrary , such that when my App references it, Visual Studio will automatically copy the Library to target bin folder. Usually I did that by using pre-build or post-build events and adding custom scripts. But hey,

Impact of adding dll reference vs project reference

由 我的未来我决定 提交于 2019-12-11 12:38:23
问题 Is there any build time impact ? We have around 30 projects in our .Net solution and they shared projects are added by project reference. I am thinking to change to dll reference instead to see if there is any build performance gain. Did anyone have experience on similar lines ? Please share your thoughts. 回答1: Yes, there is potentially a huge impact depending on how you have your CI set up. The solution to this is to group logical sections of your application (data access, presentation,

Adding programmatically in C# a project reference (as opposed to an assembly reference) via EnvDTE

由 可紊 提交于 2019-12-11 03:07:29
问题 In visual studio when you add a reference to an existing project in your solution in the .csproj file it ends up like so: <ProjectReference Include="..\TestProject2\TestProject2.csproj"> <Project>{15EC8369-B0C5-4F71-A366-19042F450A2D}</Project> <Name>TestProject2</Name> </ProjectReference> If I add a reference to an assembly DLL via EnvDTE: var p = _project as VsProject; p.References.Add(<path to assembly DLL>); it ends like this: <Reference Include="TestProject2.csproj"> <HintPath>..

Typescript 3 project reference with third party library (from npm)

由 假装没事ソ 提交于 2019-12-10 10:57:37
问题 I am using Typescript and am trying to build a background sync with service worker. Someone suggested I should do this: You can split your project into multiple parts with separate tsconfig.json files: one part that includes the dom lib and one part that includes the webworker lib. You can make another part for common code that doesn't depend on either library. You can use project references to help automate the build. If this doesn't fully solve the problem, please update the question to

Typescript 3 project reference with third party library (from npm)

由 痞子三分冷 提交于 2019-12-06 07:59:20
I am using Typescript and am trying to build a background sync with service worker. Someone suggested I should do this: You can split your project into multiple parts with separate tsconfig.json files: one part that includes the dom lib and one part that includes the webworker lib. You can make another part for common code that doesn't depend on either library. You can use project references to help automate the build. If this doesn't fully solve the problem, please update the question to describe the outstanding issues. First, I want to acknowledge I might fundamentally misuse project

dotnet pack project references

由 落花浮王杯 提交于 2019-12-05 13:21:43
问题 I quite like separating functionality across a few assemblies, for example a facade to a data provider, contracts for the data provider and the data provider implementation itself... to my mind, it makes it easy to unit test the individual components of a piece of functionality and easy to swap out one thing in the future (in the case of my example, it makes the data provider easy to swap out). If I create a solution with 3 projects and use project references, when I dotnet-build on the entry
订阅 project-reference