Windows 10: APP Data File Issue - 118 GB of Roaming and Local Data has overloaded my 256G SSD C:/ Drive...

Joanne needs your help · Dec 8, 2023

Hi, I am looking for some assistance please from anyone who is tech savvy that may be able to lend me a hand.**** My issue is as huge Hidden App Data File of 118GB that filling up my C:/ Drive which I tried to move/migrate to a D:/ drive but windows system preventing move**** Details: I have a Windows based laptop with the main drive a 256G SSD and the laptop also has an additional secondary drive- It is a 1T internal D: Drive.There is only one user on this laptop meI am using programs such as Adobe creative cloud, Microsoft teams and Microsoft office. All other personal files including

:)

Brink · Dec 8, 2023

Getting Started with Roaming App Data

Users today are mobile, transitioning from one device to the next throughout the day. Increasingly, these same users expect (or even demand) to take their data with them. Fortunately for us, roaming app data makes this a reality.
Today, we kick off a two-post series that explores how to use roaming app data to give your users a truly mobile experience. In today’s blog post, we’ll explain what roaming data is, how it works, and some ways you can use it in your own app. Finally, we’ll also cover versioning and conflict resolution.

Roaming app data

Roaming app data is the way in which all Universal Windows Platform (UWP) apps keep data in sync across multiple devices. It allows you, the developer, to create apps that help users carry data such as user profiles or documents from one device to the next. Generally speaking, roaming app data breaks down into three main categories:

App data is the data your application requires to function. This data needs to be in sync across all devices.

User data is any data that the user initiates via the application that will synchronize across all devices. For example, if you use your Microsoft account to store Microsoft Office files in the cloud from your desktop and then open Microsoft Office on your laptop, you will be presented with a list of your recent files.

App settings are any configuration settings for an app that will stay in sync across all devices. Think of your profile settings in Visual Studio 2015.

Before we get started digging into the API, it’s important to understand that you have two main points of entry into your roaming app data:

RoamingSettings

RoamingFolder

RoamingSettings

The built-in ApplicationData.RoamingSettings property, which is of the type ApplicationDataContainer, stores its data as a dictionary key/value pair with a string for the key. The key of each setting can be up to 255 characters long and the value for each setting can be no more than 8K bytes in size. Bear in mind, however, that you can only store the following data types:

UInt8, Int16, UInt16, Int32, UInt32, Int64, UInt64, Single, Double

Boolean

Char16, String

DateTime,TimeSpan

GUID, Point, Size,Rect

ApplicationDataCompositeValue

Although you should choose the data type that works best for you and your specific app, ApplicationDataCompositeValue in the above list is the recommended choice. Unlike the other types, which have an 8k-byte limit, this type allows you to store up to 64K bytes. Critically, it also lets you store a subset of settings or categorize your settings...
Click to expand...

Read more: Getting Started with Roaming App Data | Building Apps for Windows

Jarfaru · Dec 8, 2023

App data roaming file at startup?

The option is open or save as. In a box when i get to my desktop when windows 10 loads. That's it and i opened it with note pad and that's what shows in the post above. Its a 46kb sized file of all that stuff. The file path is c:.app/data/roaming/77b8df.1945a74

Brink · Dec 8, 2023

Getting started storing app data locally

When thinking about your app data, one aspect to consider is data lifetime. In general, when it comes to the lifetime of data, you have two options: local data, which exists as long as the app that created it remains installed, and roaming data, that will continue existing online even after your app is uninstalled. If you want your data to be roamed/synced and live independently of a single app installation you have different options available, such as the roaming app data feature discussed in the recent blog post series on that topic or by using a cloud data provider, such as OneDrive or Azure.

In today’s blog post, we will talk about local data, or data that is tied to the specific device where it was created. We will be looking at the different features that the Universal Windows Platform provides you with to do this, examples, and best practices.

Types of app data

There are two types of app data: settings and files.

Settings. Use settings to store app state and user preferences. The Universal Windows Platform (UWP) provides APIs to easily store and retrieve settings. The data types you can use in app settings are:

UInt8, Int16, UInt16, Int32, UInt32, Int64, UInt64, Single, Double

Boolean

Char16, String

DateTime, TimeSpan

GUID, Point, Size, Rect

ApplicationDataCompositeValue—a set of related app settings that must be serialized and deserialized atomically

Files. Use files to store binary data or to serialize your own custom types.

Storing app data locally

When an app is installed, the system creates a per-user app data container on the device. This app data container is within the app sandbox, which means no other app will be able to access it. The system will preserve the content of the data container when the app is updated and will remove it when the user uninstalls the app.

As a developer, you have three locations available in the app data container to store data locally:

Local

LocalCache

Temporary

Local

Local can contain both files (LocalFolder) and settings (LocalSettings) and should be used for any information that is of user value and can’t easily be recreated or downloaded. Data stored in Local can be backed up by the system if the device supports App Data Backup. Because of this, you should avoid using Local to store cached or temporary files that you could create or fetch again on demand.

App Data Backup

During a device backup operation, the system will grab any app data in Local and store it as part of a device backup image in OneDrive. If the user resets or replaces the device, he or she will be given the choice to restore a previous backup, which will restore the app data in Local as part of the app’s installation. Note that by not storing data in Local you will effectively be opting out of backup for your app.
Best practices for Local

Use for data with user value that can’t be recreated or downloaded by your app. If you place cached content or throwaway data in Local you are wasting user storage on OneDrive and delaying how long it takes to install your app during a device restore.

Use for settings that are unique to a device. In general, it is desirable to have common user settings on all of the user’s devices. However if you have settings that you don’t want roamed you should store them in Local.

Do not store credentials in Local. In order to offer the best user experience around credentials you should be using the Credential Locker feature.

Avoid it for data tied to specific hardware. If you have data that can only be consumed on the same physical device where it was created do not place in Local, because the user may choose to restore this data to a different device. One example of data tied to specific hardware is anything derived from device ID.

Using LocalFolder

To read or write files in LocalFolder, you must use the ApplicationData.LocalFolder property; you will get back a StorageFolder. You can then use StorageFolder.CreateFileAsync and StorageFolder.GetFileAsync to write and read files.
Click to expand...

Read more: Getting started storing app data locally | Building Apps for Windows

Windows 10: APP Data File Issue - 118 GB of Roaming and Local Data has overloaded my 256G SSD C:/ Drive...

APP Data File Issue - 118 GB of Roaming and Local Data has overloaded my 256G SSD C:/ Drive...

APP Data File Issue - 118 GB of Roaming and Local Data has overloaded my 256G SSD C:/ Drive...

APP Data File Issue - 118 GB of Roaming and Local Data has overloaded my 256G SSD C:/ Drive...

APP Data File Issue - 118 GB of Roaming and Local Data has overloaded my 256G SSD C:/ Drive... - Similar Threads - APP Data File

APP Data File Issue - 118 GB of Roaming and Local Data has overloaded my 256G SSD C:/ Drive...

APP Data File Issue - 118 GB of Roaming and Local Data has overloaded my 256G SSD C:/ Drive...

I do not understand how my Apps are taking 286 GB when my PC has a 118 GB SSD, Is this...

App roaming data location in File Explorer.

C: drive and DATA drive

C: and Data: issue

Script File in User>App Data>Roaming

App data roaming file at startup?

Getting Started with Roaming App Data