Cyclomatic
Cyclomatic
PostsComments
CC#
Created by Cyclomatic on 1/29/2025 in #help
IoC and messy factory methods
Haha , ask anyway! I also work in net core in other projects
25 replies
CC#
Created by Cyclomatic on 1/29/2025 in #help
IoC and messy factory methods
yes, .net framework 4.8 to be exact
25 replies
CC#
Created by Cyclomatic on 1/29/2025 in #help
IoC and messy factory methods
just .net fw unfortunately
25 replies
CC#
Created by Cyclomatic on 1/29/2025 in #help
IoC and messy factory methods
I actually thought that the abstractions were applicable to all containers, but I could be wrong. That is to say that if I have a servicecollectionextensions class using Dependency.Abstractions, I could consume that with an autofac container - but I could be wrong!
25 replies
CC#
Created by Cyclomatic on 1/29/2025 in #help
IoC and messy factory methods
Mmm I don't know about that - what's the issue with refrencing the Abstractions nupkg
25 replies
CC#
Created by Cyclomatic on 1/29/2025 in #help
IoC and messy factory methods
Nope!
25 replies
CC#
Created by Cyclomatic on 1/29/2025 in #help
IoC and messy factory methods
I guess my concern is that I have to actually introduce an implementation of an ioc container rather than just using the abstractions
25 replies
CC#
Created by Cyclomatic on 1/29/2025 in #help
IoC and messy factory methods
Thanks, yeah I thought that might be the best way to go about it...
25 replies
CC#
Created by Cyclomatic on 9/27/2024 in #help
Directory.Build.props
thanks
22 replies
CC#
Created by Cyclomatic on 9/27/2024 in #help
Directory.Build.props
weird, you're right, that's the one. i did try it but it hadn't worked as expected. but now it seems to
22 replies
CC#
Created by Cyclomatic on 9/27/2024 in #help
Directory.Build.props
hmm
22 replies
CC#
Created by Cyclomatic on 9/27/2024 in #help
Directory.Build.props
yeah I tried that, but I think that was giving me the path of the .csproj rather than the props file
22 replies
CC#
Created by Cyclomatic on 9/27/2024 in #help
Directory.Build.props
so if not through a build props file, how can I achieve what I want - keep the csproj agnostic about where it builds the output file
22 replies
CC#
Created by Cyclomatic on 9/27/2024 in #help
Directory.Build.props
i dont understand what you are saying. the files are already being built and output to a common directory from all projects in my repo. i just want to achieve the same thing using a Directory.Build.props file. Given the folder structure, I need the Directory.Build.props to specify the output folder for all projects and the only I see to achieve this is by knowing the path of the Directory.Build.props file from the file itself. let's not worry about nuget for the time being, one step at a time 🙂
22 replies
CC#
Created by Cyclomatic on 9/27/2024 in #help
Directory.Build.props
I wanto share a project from one repo in another repo, and hence trying to introduce the Dependency.Build.props file to get around some issues I am having in setting the output directory in the project itself
22 replies
CC#
Created by Cyclomatic on 9/27/2024 in #help
Directory.Build.props
all my projects are already being built to the same directory but each project specifies the output path. there's also a nuget.config at the root of the repo that specifies where the nuget packages need to be output
22 replies
CC#
Created by Cyclomatic on 9/27/2024 in #help
Directory.Build.props
it is already not pleasant 😄
22 replies
CC#
Created by Cyclomatic on 6/21/2024 in #help
XML Deserialization
I actually want the index for all XmlElements, not just header and title, so not ideal above
28 replies