Andras/BoundlessFlowCampus2K
4
7
Fork 0
Code Issues 90 Pull requests 7 Projects Releases Packages Wiki Activity Actions

Repository Solution file is broken after weekly merge/restructure #405

New issue
Closed
opened 2026-04-17 09:41:42 +00:00 by f21marfo · 6 comments
f21marfo commented 2026-04-17 09:41:42 +00:00
Collaborator
Copy link

The solution BoundlessFlowCampus2k.slnx is currently broken with incorrect and missing directory references.

Can currently be worked around by deleting the file and letting VS Code generate its own .sln file.

The solution BoundlessFlowCampus2k.slnx is currently broken with incorrect and missing directory references. Can currently be worked around by deleting the file and letting VS Code generate its own .sln file.
a24timsv commented 2026-04-20 07:30:39 +00:00
Collaborator
Copy link

Is this after or before the merge of #364? I can load the solution perfectly fine (15 projects). Have you fetched recently to see if any new changes are available? Can you show the error in question?

Is this after or before the merge of #364? I can load the solution perfectly fine (15 projects). Have you fetched recently to see if any new changes are available? Can you show the error in question?
f21marfo commented 2026-04-20 08:19:52 +00:00
Author
Collaborator
Copy link

After the merge. We discussed it last week. At the time of writing there no new changes.
image

After the merge. We discussed it last week. At the time of writing there no new changes. ![image](/attachments/144d01b0-4c76-4d8c-b93e-21d91dedfb9b)
image.png
80 KiB
a24timsv commented 2026-04-20 08:25:58 +00:00
Collaborator
Copy link

Those look like the old paths.

BoundlessFlowCampus2K\middleware\middleware.csproj became BoundlessFlowCampus2K\middleware\middleware\middleware.csproj when #364 merged for example.

Could you send the slnx file or a screenshot of the content?

Those look like the old paths. BoundlessFlowCampus2K\middleware\middleware.csproj became BoundlessFlowCampus2K\middleware\middleware\middleware.csproj when #364 merged for example. Could you send the slnx file or a screenshot of the content?
f21marfo commented 2026-04-20 08:32:04 +00:00
Author
Collaborator
Copy link

The file that comes up on my branch thati created friday from Team_1_Week_2, looks like this. image

I've been pulling from origin diligently throughout my work process. However if i switch to the Team_1_Week_2 now, things do look like they should be.

The file that comes up on my branch thati created friday from Team_1_Week_2, looks like this. ![image](/attachments/e997e98c-c192-49a9-8676-9387b39785e8) I've been pulling from origin diligently throughout my work process. However if i switch to the Team_1_Week_2 now, things do look like they should be.
image.png
11 KiB
a24timsv commented 2026-04-20 08:38:20 +00:00
Collaborator
Copy link

Your branch must have been created right before the merge then, because that is the old .slnx.

When you merge your branch and create a new one this won't be an issue :)

Your branch must have been created right before the merge then, because that is the old .slnx. When you merge your branch and create a new one this won't be an issue :)
f21marfo commented 2026-04-20 08:46:29 +00:00
Author
Collaborator
Copy link

No, i created my branch on Friday, well after the merge.

No, i created my branch on Friday, well after the merge.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
#1236-edit-mode-txt
#1229-generic-themed-buttons
Add-an-option-to-set-no-image-to-image-view-1227
#1242-prog-bar-colors-fix
#1239-Remove-Vertical-Scroll
Image-view-error-1230
Make-the-card-title-and-header-of-card-uniform-1233
both_teams_week_8
team_2_week_7
team_1_week_7
temp_branch_week_7
team_2_week_6
team_1_week_6
team_2_week_5
team_1_week_5
temp_branch_week_5
team_2_week_4
team_1_week_4
week_4_temp_branch
temp-branch-week-3
team_2_week_3
team_1_week_3
team_2_week_2
team_1_week_2
temp-week-2-merge-branch
team_2_week_1
team_1_week_1
No results found.
Labels
Clear labels   
_CRITICAL_

Only use this label for critical tasks that are project-scope,and must be addressed ASAP.

  
API

   
app

   
backEnd

   
Blocked, waiting for further changes

   
bug

Something is not working

  
cleanup

Issues to cleanup the codebase (restructure folders, remove deprecated or smelly code)

  
close

Issue to close

  
design

   
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
feature request

   
frontEnd

   
help wanted

Need some help

  
invalid

Something is wrong

  
low priority

   
needs input

Issue needs input from product owner or customer

  
needs review

issue is in need of review

  
project documentation

   
question

More information is needed

  
research

   
reviewed

This Issue has been reviewed

  
script

   
security

use this for security-related issues

  
SQL

  
style

   
testing

   
topLevel

Reserved for top-level, project-wide issues.

  
wontfix

This won't be fixed

No labels
_CRITICAL_
API
app
backEnd
Blocked, waiting for further changes
bug
cleanup
close
design
duplicate
enhancement
feature request
frontEnd
help wanted
invalid
low priority
needs input
needs review
project documentation
question
research
reviewed
script
security
SQL
style
testing
topLevel
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Andras/BoundlessFlowCampus2K#405
No description provided.